CVE-2026-6100

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-04-13 18:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 22:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 9.1 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-04-13 18:16 UTC

Last modified

2026-10-26 22:10 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 9.1

Attack vector

Network

Complexity

High

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-6100.md and follow it. Check whether this project is affected by CVE-2026-6100. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge