CVE-2026-114583

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-108512 (ENISA EUVD) · GHSA-mw29-5qxh-rr87 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar" to write files outside the destination directory, subject to the permissions of the extracting process.

This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2026

Last Modified

November 2, 2026

Advisory Details (3)

Auto-updated Oct 22, 2026
Patch available. Sources: github_pr.
Web page

Mailman 3 [CVE-2026-114583] tarfile.tar_filter path traversal bypass allows writing outside the extraction directory - Security-announce - python.org

https://mail.python.org/archives/list/security-announce@python.org/thread/43JOWPRAV5DI3VZ4FUEUAZOHCATXXOCK/
GitHub pull request

gh-160097: Reject links replacing the destination in `tarfile.tar_filter`

Fix merged in python/cpython PR #160098 on 2026-10-22 — awaiting tagged release

https://github.com/python/cpython/pull/160098
Web page

`tarfile.tar_filter` doesn't handle symlinks with empty names · Issue #160097 · python/cpython · GitHub

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

Vendor Advisories for CVE-2026-114583(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-11-02 13:27 UTCEG score recompute
  3. 2026-11-02 13:27 UTCVendor advisory
  4. 2026-11-02 13:27 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87 · GitHub severity MODERATE
  5. 2026-11-02 12:42 UTCEG score recompute
  6. 2026-11-02 12:42 UTCVendor advisory
  7. 2026-11-02 12:42 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87 · GitHub severity MODERATE
  8. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-29 15:14 UTCEG score recompute
  13. 2026-10-29 15:14 UTCVendor advisory
  14. 2026-10-29 15:14 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  15. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-27 01:30 UTCEG score recompute
  18. 2026-10-27 01:29 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  19. 2026-10-27 01:13 UTCEG score recompute
  20. 2026-10-27 01:13 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-10-26 01:26 UTCEG score recompute
  23. 2026-10-26 01:26 UTCVendor advisory
  24. 2026-10-26 01:26 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  25. 2026-10-26 01:16 UTCEG score recompute
Show 15 more
  1. 2026-10-26 01:16 UTCVendor advisory
  2. 2026-10-26 01:15 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-25 14:50 UTCEG score recompute
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-23 16:46 UTCEG score recompute
  7. 2026-10-23 16:46 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-23 01:27 UTCEG score recompute
  10. 2026-10-23 01:27 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  11. 2026-10-23 00:42 UTCEG score recompute
  12. 2026-10-23 00:41 UTCGHSA enrichmentGHSA-mw29-5qxh-rr87
  13. 2026-10-22 21:31 UTCEG score recompute
  14. 2026-10-22 21:11 UTCEG score recomputeFirst assessed: 6.9 MEDIUM
  15. 2026-10-22 21:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-114583?
CVE-2026-114583 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar" to write files…
When was the CVE record for CVE-2026-114583 published?
The CVE record for CVE-2026-114583 was published on October 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-114583 actively exploited?
CVE-2026-114583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114583?
CVE-2026-114583 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114583?
A fix for CVE-2026-114583 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114583 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-114583

Explore →

Is Your Infrastructure Affected by CVE-2026-114583?

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