What is CVE-2024-56327?

CVE-2024-56327 is a high-severity code injection vulnerability in pyrage (pip), affecting versions >= 1.2.0, < 1.2.3. It is fixed in 1.2.3. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2024-56327?

CVE-2024-56327 has a CVSS score of 9.8 (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 pyrage are affected by CVE-2024-56327?

pyrage (pip) versions >= 1.2.0, < 1.2.3 is affected.

Is there a fix for CVE-2024-56327?

Yes. CVE-2024-56327 is fixed in 1.2.3. Upgrade to this version or later.

Is CVE-2024-56327 exploitable, and should I be worried?

Whether CVE-2024-56327 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-2024-56327 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.

CVE-2024-56327 in pyrage

Q: How severe is CVE-2024-56327?

CVE-2024-56327 has a CVSS score of 9.8 (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 pyrage are affected by CVE-2024-56327?

pyrage (pip) versions >= 1.2.0, < 1.2.3 is affected.

Q: Is there a fix for CVE-2024-56327?

Yes. CVE-2024-56327 is fixed in 1.2.3. Upgrade to this version or later.

Q: Is CVE-2024-56327 exploitable, and should I be worried?

Whether CVE-2024-56327 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-2024-56327 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-2024-56327?

Upgrade pyrage to 1.2.3 or later.

Summary

pyrage vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary execution

pyrage uses the Rust age crate for its underlying operations, and age is vulnerable to GHSA-4fg7-vxc8-qx5w.

All details of GHSA-4fg7-vxc8-qx5w are relevant to pyrage for the versions specified in this advisory. See GHSA-4fg7-vxc8-qx5w for full details.

Versions of pyrage before 1.2.0 lack plugin support and are therefore not affected.

An equivalent issue was fixed in the reference Go implementation of age, see advisory GHSA-32gq-x56h-299c.

Thanks to ⬡-49016 for reporting this issue.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2024-56327 has a CVSS score of 9.8 (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 (1.2.3); upgrading removes the vulnerable code path.

Affected versions

pyrage (>= 1.2.0, < 1.2.3)

Security releases

pyrage → 1.2.3 (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

Upgrade pyrage to 1.2.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-56327? CVE-2024-56327 is a high-severity code injection vulnerability in pyrage (pip), affecting versions >= 1.2.0, < 1.2.3. It is fixed in 1.2.3. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2024-56327? CVE-2024-56327 has a CVSS score of 9.8 (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 pyrage are affected by CVE-2024-56327? pyrage (pip) versions >= 1.2.0, < 1.2.3 is affected.
Is there a fix for CVE-2024-56327? Yes. CVE-2024-56327 is fixed in 1.2.3. Upgrade to this version or later.
Is CVE-2024-56327 exploitable, and should I be worried? Whether CVE-2024-56327 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-2024-56327 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-2024-56327? Upgrade pyrage to 1.2.3 or later.