CVE-2026-11972

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 23, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

Mailman 3 [CVE-2026-11972] tarfile opened in streaming mode mishandles EOF - Security-announce - python.org

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

gh-151981: Make tarfile._Stream.seek break at EOF

Fix merged in python/cpython PR #151982 on 2026-06-23 — awaiting tagged release

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

tarfile._Stream.seek ignores EOF · Issue #151981 · python/cpython · GitHub

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

Vendor Advisories for CVE-2026-11972(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3-14-main-3.14.7-1.hum12026-08-13redhat
redhatpython3-13-main-3.13.15-1.hum12026-08-13redhat
redhatpython3-12-main-3.12.13-3.3.hum12026-07-05redhat
redhatpython3-14-main-3.14.6-1.2.hum12026-07-05redhat
redhatpython3-11-main-3.11.15-4.4.hum12026-07-05redhat
redhatpython3-13-main-3.13.14-1.2.hum12026-07-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 4 ecosystems)
Debian:11(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python2.72.7.18-10 ... 2.7.18-9 (10 versions)——
python3.93.9.10-1 ... 3.9.9-4 (29 versions)——
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (8 versions)——
python3.143.14.0-1 ... 3.14.6-1 (24 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.9-1 (28 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (12 versions)——

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 165× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 265 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:46 UTCVendor advisory
  3. 2026-08-20 19:46 UTCGHSA enrichment
  4. 2026-08-20 07:45 UTCEG score recompute
  5. 2026-08-20 07:45 UTCVendor advisory
  6. 2026-08-20 07:45 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 04:47 UTCEG score recompute
  9. 2026-08-19 04:47 UTCVendor advisory
  10. 2026-08-19 04:47 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:39 UTCVendor advisory
  13. 2026-08-17 13:39 UTCGHSA enrichment
  14. 2026-08-17 01:38 UTCEG score recompute
  15. 2026-08-17 01:38 UTCVendor advisory
  16. 2026-08-17 01:38 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:37 UTCEG score recompute
  19. 2026-08-16 13:37 UTCVendor advisory
  20. 2026-08-16 13:37 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-16 01:28 UTCVendor advisory
  23. 2026-08-16 01:28 UTCGHSA enrichment
  24. 2026-08-15 13:27 UTCEG score recompute
  25. 2026-08-15 13:27 UTCVendor advisory
Show 75 more
  1. 2026-08-15 13:27 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-15 01:26 UTCVendor advisory
  4. 2026-08-15 01:26 UTCGHSA enrichment
  5. 2026-08-14 13:26 UTCVendor advisory
  6. 2026-08-14 13:26 UTCGHSA enrichment
  7. 2026-08-14 01:25 UTCEG score recompute
  8. 2026-08-14 01:25 UTCVendor advisory
  9. 2026-08-14 01:25 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 13:24 UTCVendor advisory
  12. 2026-08-13 13:24 UTCGHSA enrichment
  13. 2026-08-13 01:23 UTCEG score recompute
  14. 2026-08-13 01:23 UTCVendor advisory
  15. 2026-08-13 01:23 UTCGHSA enrichment
  16. 2026-08-13 00:41 UTCEG score recompute
  17. 2026-08-13 00:41 UTCVendor advisory
  18. 2026-08-13 00:41 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-12 13:35 UTCVendor advisory
  21. 2026-08-12 13:35 UTCGHSA enrichment
  22. 2026-08-12 01:34 UTCEG score recompute
  23. 2026-08-12 01:34 UTCVendor advisory
  24. 2026-08-12 01:34 UTCGHSA enrichment
  25. 2026-08-11 13:42 UTCEPSS rescore
  26. 2026-08-11 13:34 UTCVendor advisory
  27. 2026-08-11 13:34 UTCGHSA enrichment
  28. 2026-08-11 01:33 UTCEG score recompute
  29. 2026-08-11 01:33 UTCVendor advisory
  30. 2026-08-11 01:33 UTCGHSA enrichment
  31. 2026-08-10 23:59 UTCEPSS rescore
  32. 2026-08-10 13:32 UTCVendor advisory
  33. 2026-08-10 13:32 UTCGHSA enrichment
  34. 2026-08-10 01:27 UTCEG score recompute
  35. 2026-08-10 01:27 UTCVendor advisory
  36. 2026-08-10 01:27 UTCGHSA enrichment
  37. 2026-08-09 13:46 UTCEPSS rescore
  38. 2026-08-09 13:26 UTCVendor advisory
  39. 2026-08-09 13:26 UTCGHSA enrichment
  40. 2026-08-09 01:26 UTCEG score recompute
  41. 2026-08-09 01:26 UTCVendor advisory
  42. 2026-08-09 01:26 UTCGHSA enrichment
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-08 13:25 UTCVendor advisory
  45. 2026-08-08 13:25 UTCGHSA enrichment
  46. 2026-08-08 01:24 UTCEG score recompute
  47. 2026-08-08 01:24 UTCVendor advisory
  48. 2026-08-08 01:24 UTCGHSA enrichment
  49. 2026-08-07 13:23 UTCVendor advisory
  50. 2026-08-07 13:23 UTCGHSA enrichment
  51. 2026-08-07 01:23 UTCEG score recompute
  52. 2026-08-07 01:23 UTCVendor advisory
  53. 2026-08-07 01:22 UTCGHSA enrichment
  54. 2026-08-06 13:46 UTCEPSS rescore
  55. 2026-08-06 13:22 UTCVendor advisory
  56. 2026-08-06 13:22 UTCGHSA enrichment
  57. 2026-08-06 01:21 UTCEG score recompute
  58. 2026-08-06 01:21 UTCVendor advisory
  59. 2026-08-06 01:21 UTCGHSA enrichment
  60. 2026-08-06 00:50 UTCEG score recompute
  61. 2026-08-06 00:50 UTCVendor advisory
  62. 2026-08-06 00:50 UTCGHSA enrichment
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 14:28 UTCEG score recompute
  65. 2026-08-05 14:28 UTCVendor advisory
  66. 2026-08-05 14:28 UTCGHSA enrichment
  67. 2026-08-05 13:49 UTCEG score recompute
  68. 2026-08-05 13:49 UTCVendor advisory
  69. 2026-08-05 13:49 UTCGHSA enrichment
  70. 2026-08-05 01:19 UTCEG score recompute
  71. 2026-08-05 01:19 UTCVendor advisory
  72. 2026-08-05 01:19 UTCGHSA enrichment
  73. 2026-08-05 00:51 UTCEG score recompute
  74. 2026-08-05 00:51 UTCVendor advisory
  75. 2026-08-05 00:51 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-11972?
CVE-2026-11972 is a high vulnerability published on June 23, 2026. 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.
When was CVE-2026-11972 disclosed?
CVE-2026-11972 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11972 actively exploited?
CVE-2026-11972 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-11972?
CVE-2026-11972 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-11972?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11972, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11972

Explore →

Is Your Infrastructure Affected by CVE-2026-11972?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs