Build corruption when using `PYO3_CONFIG_FILE` environment variable
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | pyo3 (crates.io) | 0.23.0 to before 0.23.3 | 0.23.3 | Patch available | GHSA-vxcf-c7mx-pg53 |
- pyo3 (crates.io) Vendor— Affected 0.23.0 to before 0.23.3 Fixed in 0.23.3 Patch available GHSA-vxcf-c7mx-pg53
Remediation
- Fix · GHSA-vxcf-c7mx-pg53 pyo3 (crates.io) Fixed in 0.23.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-vxcf-c7mx-pg53
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences