Skip to content

Commit 9498cb5

Browse files
davidhewittShnatselkornelski
authored
report build corruption in PyO3 0.23 (#2159)
* report build corruption in PyO3 0.23 * Update crates/pyo3/RUSTSEC-0000-0000.md Co-authored-by: Kornel <[email protected]> --------- Co-authored-by: Sergey "Shnatsel" Davidoff <[email protected]> Co-authored-by: Kornel <[email protected]>
1 parent f34e889 commit 9498cb5

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

crates/pyo3/RUSTSEC-0000-0000.md

+19
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
```toml
2+
[advisory]
3+
id = "RUSTSEC-0000-0000"
4+
package = "pyo3"
5+
date = "2024-12-04"
6+
url = "https://github.com/PyO3/pyo3/issues/4757"
7+
categories = ["memory-corruption"]
8+
keywords = ["memory-corruption", "ffi", "corrupted-build"]
9+
10+
[versions]
11+
patched = [">= 0.23.3"]
12+
unaffected = ["< 0.23.0"]
13+
```
14+
15+
# Build corruption when using `PYO3_CONFIG_FILE` environment variable
16+
17+
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.
18+
19+
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.

0 commit comments

Comments
 (0)