CVE-2026-11940

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 48% 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 — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself.  The extraction fallback validated the symlink at it's archived location but recreated it at the hardlink's shallower path, letting a relative target the filter judged contained escape the destination directory.  This allowed a malicious tar archive to create a symlink pointing outside the destination, enabling out-of-destination file reads or writes. This was an incomplete fix of CVE-2025-4330.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity78% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

June 23, 2026

Last Modified

August 13, 2026

Advisory Details (3)

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

Mailman 3 [CVE-2026-11940] tarfile extraction filter bypass allows escaping the destination directory - Security-announce - python.org

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

gh-151558: Fix symlink escape via `tarfile` hardlink-extraction fallback

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

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

`tarfile.extractall(filter='data')` allows symlink escape through hardlink-extraction fallback · Issue #151558 · python/cpython · GitHub

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

Vendor Advisories for CVE-2026-11940(8)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3-14-main-3.14.7-1.hum12026-08-13redhat
redhatdiscovery/discovery-server-rhel9:17866385732026-08-13redhat
redhatpython3-13-main-3.13.15-1.hum12026-08-13redhat
redhatpython3.9-0:3.9.25-7.el9_8.32026-08-12redhat
redhatpython3-14-main-3.14.6-1.4.hum12026-07-10redhat
redhatpython3-13-main-3.13.14-1.4.hum12026-07-10redhat
redhatpython3-11-main-3.11.15-5.2.hum12026-07-10redhat
redhatpython3-12-main-3.12.13-3.5.hum12026-07-10redhat

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

(8 across 4 ecosystems)
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:11(2)
PackageVulnerable rangeFixed inDependents
python2.72.7.18-10 ... 2.7.18-9 (10 versions)——
python3.93.9.10-1 ... 3.9.9-4 (29 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)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python3.113.11.2-6 ... 3.11.9-1 (28 versions)——

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11940?
CVE-2026-11940 is a high vulnerability published on June 23, 2026. tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself. The extraction fallback validated the symlink at it's archived location but recreated it at the hardlink's shallower…
When was CVE-2026-11940 disclosed?
CVE-2026-11940 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-11940 actively exploited?
CVE-2026-11940 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.2% of all scored CVEs.
What is the CVSS score of CVE-2026-11940?
CVE-2026-11940 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-11940?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11940, 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-11940

Explore →

Is Your Infrastructure Affected by CVE-2026-11940?

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

Start Free Scan →Browse All CVEs