Home

Description

Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.

PUBLISHED Reserved 2026-04-10 | Published 2026-04-13 | Updated 2026-04-14 | Assigner PSF




CRITICAL: 9.1CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-416 Use after free

CWE-787 Out-of-bounds write

Product status

Default status
unaffected

Any version before 3.15.0
affected

Credits

Ryan Hileman reporter

Stan Ulbrych remediation developer

Seth Larson coordinator

Stan Ulbrych finder

Ryan Hileman finder

References

www.openwall.com/lists/oss-security/2026/04/13/10

github.com/python/cpython/pull/148396 patch

mail.python.org/.../thread/HTWB2Z6KT5QQX4RYEZAFININDHNOSIF3/ vendor-advisory

github.com/python/cpython/issues/148395 issue-tracking

github.com/...ommit/6a5f79c8d7bbf22b083b240910c7a8781a59437d patch

github.com/...ommit/8fc66aef6d7b3ae58f43f5c66f9366cc8cbbfcd2 patch

github.com/...ommit/c3cf71c3366fe49acb776a639405c0eea6169c20 patch

github.com/...ommit/47128e64f98c3a20271138a98c2922bea2a3ee0e patch

github.com/...ommit/e20c6c9667c99ecaab96e1a2b3767082841ffc8b patch

cve.org (CVE-2026-6100)

nvd.nist.gov (CVE-2026-6100)

Download JSON