CVE-2026-11972

Home/CVE/When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly h

CVE

↯ PDF report

When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly h

When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly handle EOF, meaning an archive could be parsed in an infinite loop.

Monitor

⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2026-11972, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

◆

ATT&CK techniques

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1498.001 · Direct Network Flood T1498.002 · Reflection Amplification T1499 · Endpoint Denial of Service T1499.001 · OS Exhaustion Flood T1499.002 · Service Exhaustion Flood T1499.003 · Application Exhaustion Flood T1499.004 · Application or System Exploitation

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-125 · Flooding CAPEC-CAPEC-130 · Excessive Allocation CAPEC-CAPEC-147 · XML Ping of the Death CAPEC-CAPEC-197 · Exponential Data Expansion CAPEC-CAPEC-229 · Serialized Data Parameter Blowup CAPEC-CAPEC-230 · Serialized Data with Nested Payloads CAPEC-CAPEC-231 · Oversized Serialized Data Payloads CAPEC-CAPEC-469 · HTTP DoS CAPEC-CAPEC-482 · TCP Flood CAPEC-CAPEC-486 · UDP Flood CAPEC-CAPEC-487 · ICMP Flood CAPEC-CAPEC-488 · HTTP Flood

⬡

Weakness Classification

CWE-252Unchecked Return Value
CWE-606Unchecked Input for Loop Condition
CWE-770Allocation of Resources Without Limits or Throttling

▤

Related CVEs

CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.

CVE-2002-1372 Common Unix Printing System (CUPS) 1.1.14 through 1.1.17 does not properly check... same CWE-252 HIGH CVE-1999-0199 manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement... same CWE-252 CRITICAL CVE-2005-4360 The URL parser in Microsoft Internet Information Services (IIS) 5.1 on Windows X... 2 same CWE-252 CVE-2007-3798 Integer overflow in print-bgp.c in the BGP dissector in tcpdump 3.9.6 and earlie... 1 same CWE-252 CRITICAL CVE-2019-25624 Liquid Studio 2.17 contains a denial of service vulnerability that allows local ... same CWE-606 MEDIUM CVE-2022-3252 Improper detection of complete HTTP body decompression SwiftNIO Extras provides ... same CWE-606 HIGH CVE-2023-3446 Issue summary: Checking excessively long DH keys or parameters may be very slow.... same CWE-606 MEDIUM CVE-2023-3817 Issue summary: Checking excessively long DH keys or parameters may be very slow.... same CWE-606 MEDIUM

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://github.com/python/cpython/issues/151981

https://github.com/python/cpython/pull/151982

https://mail.python.org/archives/list/[email protected]/thread/AXPSKKTSRKXTTJULW3XSIC74WZNAAPPB/