CVE-2026-11972Disclosure

LOWCVSS 8.2 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly handle EOF, making archive parsing take exponentially longer.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-252CWE-606CWE-770

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

2 mentions across 1 observed day

What's happening

Technical details provided in 2 signals
Disclosure: 2 classified signals
2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d

Signal classification1 categories

Disclosure

2100.0%

Referenced assets2 URLs

By indicator

Full discourse2 posts

Infoflowcloud@infoflowcloud91d
Disclosure
🚨*CVE* CVE-2026-11972 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 … https://www.cve.org/CVERecord?id=CVE-2026-11972 ----- Traducción: CVE-2026-11972 Cua… http://infoflow.cloud`
Post summary
The post announces CVE-2026-11972, describing an EOF handling flaw in Python's tarfile module without providing patches, exploits, or PoC evidence.
0000029
88 followersView on X
CVE@CVEnew91d
Disclosure
CVE-2026-11972 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 … https://www.cve.org/CVERecord?id=CVE-2026-11972
Post summary
The text outlines CVE‑2026‑11972 as an EOF handling flaw in Python’s tarfile module but offers no PoC, exploit, active attack claims, or patch details.
00000676
57.7K followersView on X

Explore more

Back to dashboard