Finding and attribution
The CPython issue describes a possible use-after-free when reused LZMA, BZ2 or zlib decompressor objects encounter memory pressure. The issue was fixed in the relevant branches.
Product: CPython (LZMA, BZ2 and zlib decompressor objects). AI system: Xint Code. Team / organization: Xint; affected product vendor.
CVE identifiers: CVE-2026-6100.
AI and human contribution (source account): Xint says its researcher ran the whole CPython source through Xint Code Fast mode without an operator prompt and received this as the highest-severity result roughly 30 minutes later. A human then validated/reported it; Xint’s chronology says the fix followed quickly.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The cited sources document a reported vulnerability and remediation but do not establish the defenders’ prior knowledge or exploitation status.
Remediation status: fix documented. CPython fixes are documented in commits/branches. The cited sources do not establish exploitation in the wild; the “0day” phrasing is Xint’s title and is not treated here as independently established status.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 13 Apr 2026. AI attribution dated 13 Apr 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Critical · highest recorded score 9.1. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-6100: CVSS 4.0 · 9.1 (Critical) ·
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N· Assessment scenarios: GENERAL. PSF (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-6100: CVSS 3.1 · 8.1 (High) ·
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. redhat-SADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2026-6100: other.
Prerequisites / affected scope: Only if allocation failure raises MemoryError during decompression and the same decompressor instance is reused afterward, the dangling pointer permits use-after-free. One-shot helpers and instances not reused after the error are not affected. No further consequence established..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: CPython fixes are documented in commits/branches. The cited sources do not establish exploitation in the wild; the “0day” phrasing is Xint’s title and is not treated here as independently established status.