What is CVE-2022-41892?

CVE-2022-41892 is a high-severity SQL injection vulnerability in arches (pip), affecting versions <= 6.1.1. It is fixed in 6.1.2, 6.2.1, 7.2.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2022-41892?

CVE-2022-41892 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of arches are affected by CVE-2022-41892?

arches (pip) versions <= 6.1.1 is affected.

Is there a fix for CVE-2022-41892?

Yes. CVE-2022-41892 is fixed in 6.1.2, 6.2.1, 7.2.0. Upgrade to this version or later.

Is CVE-2022-41892 exploitable, and should I be worried?

Whether CVE-2022-41892 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-41892 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-41892?

Upgrade: arches to 6.1.2 or later, arches to 6.2.1 or later, arches to 7.2.0 or later.

CVE-2022-41892 in arches

Q: How severe is CVE-2022-41892?

CVE-2022-41892 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of arches are affected by CVE-2022-41892?

arches (pip) versions <= 6.1.1 is affected.

Q: Is there a fix for CVE-2022-41892?

Yes. CVE-2022-41892 is fixed in 6.1.2, 6.2.1, 7.2.0. Upgrade to this version or later.

Q: Is CVE-2022-41892 exploitable, and should I be worried?

Whether CVE-2022-41892 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-41892 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-41892?

Upgrade: arches to 6.1.2 or later, arches to 6.2.1 or later, arches to 7.2.0 or later.

Summary

Arches vulnerable to execution of arbitrary SQL

Workarounds

There are no workarounds.

General References

https://www.w3schools.com/sql/sql_injection.asp
https://en.wikipedia.org/wiki/SQL_injection

For more information

Post any questions to the Arches project forum.

Impact

With a carefully crafted web request, it's possible to execute certain unwanted sql statements against the database.
Anyone running the impacted versions (<=6.1.1, 6.2.0, >=7.0.0, <=7.1.1) should upgrade as soon as possible.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2022-41892 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.1.2, 6.2.1, 7.2.0); upgrading removes the vulnerable code path.

Affected versions

arches (<= 6.1.1) arches (= 6.2.0) arches (>= 7.0.0, <= 7.1.1)

Security releases

arches → 6.1.2 (pip) arches → 6.2.1 (pip) arches → 7.2.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem has been patched in the following versions: 6.1.2, 6.2.1, and 7.2.0
Users are strongly urged to upgrade to the most recent relevant patch.

Frequently Asked Questions

What is CVE-2022-41892? CVE-2022-41892 is a high-severity SQL injection vulnerability in arches (pip), affecting versions <= 6.1.1. It is fixed in 6.1.2, 6.2.1, 7.2.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2022-41892? CVE-2022-41892 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of arches are affected by CVE-2022-41892? arches (pip) versions <= 6.1.1 is affected.
Is there a fix for CVE-2022-41892? Yes. CVE-2022-41892 is fixed in 6.1.2, 6.2.1, 7.2.0. Upgrade to this version or later.
Is CVE-2022-41892 exploitable, and should I be worried? Whether CVE-2022-41892 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-41892 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-41892?
- Upgrade arches to 6.1.2 or later
- Upgrade arches to 6.2.1 or later
- Upgrade arches to 7.2.0 or later