Skip to content
Noroxi
NVD / CVE Program· CNA PSF

CVE-2026-6100: Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Python Software Foundation CPython 3.10.21, 3.11.16, 3.12.14; azl3 python3 3.12.9-13 on Azure Linux 3.0 3.12.9-14; azl3 python3 3.12.9-14 on Azure Linux 3.0 3.12.9-14.

Low priority for now. Upgrade to Python Software Foundation CPython 3.10.21, 3.11.16, 3.12.14; azl3 python3 3.12.9-13 on Azure Linux 3.0 3.12.9-14; azl3 python3 3.12.9-14 on Azure Linux 3.0 3.12.9-14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.1 · v4.0—No exploit Fix available
Published
Apr 13, 2026
Updated
Oct 26, 2026
EPSS
0.5% · 47th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PSF
9.1
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-6100

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
enterprise linux10.1
enterprise linux10.2
enterprise linux eus10.0
enterprise linux8
rhel aus8.4
rhel eus long life8.4
rhel aus8.6
rhel tus8.6
rhel e4s8.6
rhel tus8.8
rhel e4s8.8
enterprise linux9

and 13 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.

  • Python Software Foundation CPython

    • before 3.10.21affected · python
    • 3.11.0 and later · before 3.11.16affected · python
    • 3.12.0 and later · before 3.12.14affected · python
    • 3.13.0 and later · before 3.13.14affected · python
    • 3.14.0a1 and later · before 3.14.5rc1affected · python
    • 3.15.0a1 and later · before 3.15.0b1affected · python

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10python-unversioned-commandbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python-unversioned-commandbefore 3.12.12-3.el10_1.33.12.12-3.el10_1.3
AlmaLinux:10python3before 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-debugbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-develbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-idlebefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-libsbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-testbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3-tkinterbefore 3.12.13-2.el10_23.12.13-2.el10_2
AlmaLinux:10python3.14before 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-debugbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-develbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreadingbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-debugbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-develbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-idlebefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-libsbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-testbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-freethreading-tkinterbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-idlebefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-libsbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-testbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:10python3.14-tkinterbefore 3.14.4-2.el10_23.14.4-2.el10_2
AlmaLinux:8platform-pythonbefore 3.6.8-76.el8_10.alma.13.6.8-76.el8_10.alma.1

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-115557Distrust compromised intermediate certificates in ssl module
    37Monitor
  • CVE-2025-4517Arbitrary writes via tarfile realpath overflow
    37Monitor
  • CVE-2026-19445Use-after-free of a server-side SSLContext when sni_callback switches contexts
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-1502Apr 10, 2026 · HTTP client proxy tunnel headers not validated for CR/LF
    22Monitor
  • ← EarlierCVE-2026-3446Apr 10, 2026 · Base64 decoding stops at first padded quad by default
    24Monitor
  • Later →CVE-2026-4786Apr 13, 2026 · Incomplete mitigation of CVE-2026-4519, %action expansion for command injection to webbrowser.open()
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Python Software Foundation CPython3.10.21Vendor (CNA)
Python Software Foundation CPython3.11.16Vendor (CNA)
Python Software Foundation CPython3.12.14Vendor (CNA)
Python Software Foundation CPython3.13.14Vendor (CNA)
Python Software Foundation CPython3.14.5rc1Vendor (CNA)
Python Software Foundation CPython3.15.0b1Vendor (CNA)
azl3 python3 3.12.9-13 on Azure Linux 3.03.12.9-14 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 python3 3.12.9-14 on Azure Linux 3.03.12.9-14 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:python-unversioned-command3.12.12-3.el10_1.3 · AlmaLinux:10Package registry (OSV)
almalinux:python3.113.11.13-5.3.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:python3.11-debug3.11.13-5.3.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:python3.11-devel3.11.13-5.3.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:python3.11-idle3.11.13-5.3.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:python3.123.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-debug3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-devel3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-idle3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-libs3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-test3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3.12-tkinter3.12.12-4.el9_7.3 · AlmaLinux:9Package registry (OSV)
alpine:python33.12.14-r0 · Alpine:v3.21Package registry (OSV)
debian:python3.113.11.2-6+deb12u8 · Debian:12Package registry (OSV)
debian:python3.133.13.5-2+deb13u2 · Debian:13Package registry (OSV)
debian:python3.143.14.5~rc1-1 · Debian:14Package registry (OSV)
opensuse:python33.13.14-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:python3103.10.20-6.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3113.11.15-6.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3123.12.13-6.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3133.13.13-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python313-core3.13.14-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)

+41

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-19445170 days apartUse-after-free of a server-side SSLContext when sni_callback switches contexts
    36Monitor
  • CVE-2025-4516333 days apartUse-after-free in "unicode_escape" decoder with error handler
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records