Bug 2457932 (CVE-2026-6100) - CVE-2026-6100 python: Python: Arbitrary code execution or information disclosure via use-after-free in decompression modules
Summary: CVE-2026-6100 python: Python: Arbitrary code execution or information disclos...
Keywords:
Status: NEW
Alias: CVE-2026-6100
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2458008 2458009 2458010 2458011 2458012 2458013 2458014 2458015 2458016 2458017 2458018 2458019
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-13 18:01 UTC by OSIDB Bzimport
Modified: 2026-04-13 21:02 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-13 18:01:55 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.