This issue consolidates 13 reproducible CPython 3.15 bugs involving memory safety and concurrency.
The bugs resulted from Python security research using static analysis. Each entry has a concrete PoC in the linked version-specific Gist. Although the collection is large, these bugs warrant inspection, especially the cases producing interpreter crashes, sanitizer failures, memory corruption, or similarly concrete failures.
Bugs
AST initialization _field_types race — Concurrent descriptor replacement can reclaim a borrowed value and cause an impossible initialization decision.
The cross-version review identifies the following 78 bugs as shared across CPython 3.13, 3.14, and 3.15. Each item links to its detailed report and concrete PoC in the consolidated CPython 3.14 Gist.
structseq-type-metadata-borrow-race — Struct-sequence operations consume concurrently replaced type metadata through a borrowed dictionary value.
ElementTree is not currently not safe in FT so all issues are invalid as of now. Thdre is alsona separate issue about making etree FT-safe. So please in the future avoid dumping issues in a bulk if there is alredy an open one (or comment on that one directly)
Activity
Nievesjyl commented on Sep 8, 2026
This issue is associated with #157197 and #157196
Nievesjyl commented on Sep 8, 2026
The cross-version review identifies the following 78 bugs as shared across CPython 3.13, 3.14, and 3.15. Each item links to its detailed report and concrete PoC in the consolidated CPython 3.14 Gist.
picnixz commented on Sep 9, 2026
ElementTree is not currently not safe in FT so all issues are invalid as of now. Thdre is alsona separate issue about making etree FT-safe. So please in the future avoid dumping issues in a bulk if there is alredy an open one (or comment on that one directly)
picnixz commented on Sep 9, 2026
There are also exisring issues for array.* i believe so clean up your list first please.
Nievesjyl commented on Sep 9, 2026
Thanks for the response. We’ll do the cleanup ASAP.
Nievesjyl commented on Sep 11, 2026
We are preparing a carefully screened report that complies with CPython policy, so we are closing this issue.