How severe is GHSA-vxcf-c7mx-pg53?

No CVSS score has been assigned to GHSA-vxcf-c7mx-pg53 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vxcf-c7mx-pg53?

GHSA-vxcf-c7mx-pg53 affects the following packages: pyo3 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-vxcf-c7mx-pg53?

Update pyo3 to 0.23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vxcf-c7mx-pg53 is resolved across your whole dependency graph.

How do I detect GHSA-vxcf-c7mx-pg53 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyo3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vxcf-c7mx-pg53 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-vxcf-c7mx-pg53?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vxcf-c7mx-pg53 can be triaged on real exposure rather than presence alone.

Is GHSA-vxcf-c7mx-pg53 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vxcf-c7mx-pg53 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vxcf-c7mx-pg53 published, and has it been updated?

GHSA-vxcf-c7mx-pg53 was published on December 5, 2024 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-vxcf-c7mx-pg53 — pyo3

GHSA-vxcf-c7mx-pg53 is a security vulnerability in pyo3. A fix is available for pyo3 — see the affected versions and patch details below.

Build corruption when using `PYO3_CONFIG_FILE` environment variable

Also known asRUSTSEC-2024-0409

Published

Dec 5, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀pyo3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`pyo3`	≥ 0.23.0&&< 0.23.3	0.23.3`cargo update -p pyo3 --precise 0.23.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyo3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pyo3 to 0.23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vxcf-c7mx-pg53 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vxcf-c7mx-pg53 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vxcf-c7mx-pg53. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-vxcf-c7mx-pg53 in your dependencies?

O3 Security finds GHSA-vxcf-c7mx-pg53 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works