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 65% 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 — 3 sources updated this week
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 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)
EPSS
35.3%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 30, 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/security-announce@python.org/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(6)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 101× 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 101 total refreshes for this CVE.

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

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 June 30, 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 35.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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