What is GHSA-VXCF-C7MX-PG53?

GHSA-VXCF-C7MX-PG53 is a medium-severity security vulnerability in pyo3 (rust), affecting versions >= 0.23.0, < 0.23.3. It is fixed in 0.23.3.

Which versions of pyo3 are affected by GHSA-VXCF-C7MX-PG53?

pyo3 (rust) versions >= 0.23.0, < 0.23.3 is affected.

Is there a fix for GHSA-VXCF-C7MX-PG53?

Yes. GHSA-VXCF-C7MX-PG53 is fixed in 0.23.3. Upgrade to this version or later.

Is GHSA-VXCF-C7MX-PG53 exploitable, and should I be worried?

Whether GHSA-VXCF-C7MX-PG53 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 GHSA-VXCF-C7MX-PG53 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.

GHSA-VXCF-C7MX-PG53 in pyo3

Q: Which versions of pyo3 are affected by GHSA-VXCF-C7MX-PG53?

pyo3 (rust) versions >= 0.23.0, < 0.23.3 is affected.

Q: Is there a fix for GHSA-VXCF-C7MX-PG53?

Yes. GHSA-VXCF-C7MX-PG53 is fixed in 0.23.3. Upgrade to this version or later.

Q: Is GHSA-VXCF-C7MX-PG53 exploitable, and should I be worried?

Whether GHSA-VXCF-C7MX-PG53 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 GHSA-VXCF-C7MX-PG53 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 GHSA-VXCF-C7MX-PG53?

Upgrade pyo3 to 0.23.3 or later.

Summary

Build corruption when using PYO3CONFIGFILE environment variable

In PyO3 0.23.0 the PYO3_CONFIG_FILE environment variable used to configure builds regressed such that changing the environment variable would no longer trigger PyO3 to reconfigure and recompile. In combination with workflows using tools such as maturin to build for multiple versions in a single build, this leads to Python wheels being compiled against the wrong Python API version.

All users who distribute artefacts for multiple Python versions are encouraged to update and rebuild with PyO3 0.23.3. Affected wheels produced from PyO3 0.23.0 through 0.23.2 are highly unstable and will crash the Python interpreter in unpredictable ways.

Impact

Affected versions

pyo3 (>= 0.23.0, < 0.23.3)

Security releases

pyo3 → 0.23.3 (rust)

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 pyo3 to 0.23.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 GHSA-VXCF-C7MX-PG53? GHSA-VXCF-C7MX-PG53 is a medium-severity security vulnerability in pyo3 (rust), affecting versions >= 0.23.0, < 0.23.3. It is fixed in 0.23.3.
Which versions of pyo3 are affected by GHSA-VXCF-C7MX-PG53? pyo3 (rust) versions >= 0.23.0, < 0.23.3 is affected.
Is there a fix for GHSA-VXCF-C7MX-PG53? Yes. GHSA-VXCF-C7MX-PG53 is fixed in 0.23.3. Upgrade to this version or later.
Is GHSA-VXCF-C7MX-PG53 exploitable, and should I be worried? Whether GHSA-VXCF-C7MX-PG53 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 GHSA-VXCF-C7MX-PG53 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 GHSA-VXCF-C7MX-PG53? Upgrade pyo3 to 0.23.3 or later.

Other vulnerabilities in pyo3

CVE-IDSeverityPackage summary

GHSA-CHGR-C6PX-7XPPMediumpyo3: PyO3 has a missing `Sync` bound on `PyCFunction::new_closure` closures GHSA-36HH-V3QG-5JQ4Highpyo3: PyO3 has an Out-of-bounds Read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators GHSA-47QC-857F-7W7FHighpyo3: PyO3 has type confusion when accessing data from sublasses of subclasses of native types with `abi3` feature GHSA-PPH8-GCV7-4QJ5Lowpyo3: PyO3 Risk of buffer overflow in `PyString::from_object`CVE-2024-9979Mediumpyo3: PyO3 has a risk of use-after-free in `borrowed` reads from Python weak references