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 47% 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
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
53%
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(20)

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

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-rhel9:17888805812026-09-09redhat
redhatpython3-0:3.6.8-51.el8_8.172026-09-08redhat
redhatpython3-0:3.6.8-47.el8_6.152026-09-08redhat
redhatpython3.12-0:3.12.9-1.el9_6.102026-09-03redhat
redhatpython3.12-0:3.12.9-2.el10_0.112026-09-03redhat
redhatpython3.12-0:3.12.1-4.el9_4.152026-09-02redhat
redhatpython3.14-0:3.14.7-2.el10_22026-08-24redhat
redhatpython3.14-0:3.14.7-2.el9_82026-08-24redhat
redhatpython3.12-0:3.12.14-1.el10_22026-08-24redhat
redhatpython3.12-0:3.12.14-1.el9_82026-08-24redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatpython3.12-0:3.12.14-1.el8_102026-08-24redhat
redhatpython3-0:3.6.8-78.el8_102026-08-18redhat
redhatdiscovery/discovery-server-rhel9:17866385732026-08-13redhat
redhatpython3-14-main-3.14.7-1.hum12026-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-12-main-3.12.13-3.5.hum12026-07-10redhat
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

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

(12 across 8 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)3.13.15-1—
python3.143.14.0-1 ... 3.14.6-1 (24 versions)3.14.7-1—
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 (13 versions)——
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—3.14.7-r0—
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

(2)

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

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

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 46.6% 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