CVE-2026-19672

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Trending — 4 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The tarfile module's tar and data extraction filters created directories outside the destination for members whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The containment check used the resolved path, but intermediate directories were created from the name as given.

Only empty directories are created outside the destination. Member contents are still extracted inside it. To return to the destination the member's name must contain the destination directory's own final component, so extraction into a secure randomised directory is not affected.

This affects POSIX platforms only. On Windows, .. components are collapsed before the path reaches the filesystem, so the directories outside the destination are never created.

CVSS v3
6.3
EG Score
6.3(low)
EG Risk
33(Track)
EG Risk 33/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
Severity63% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (2)

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

Mailman 3 [CVE-2026-19672] tarfile extraction filter bypass allows creation of directories outside the destination - Security-announce - python.org

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

gh-155999: In `tarfile`, handle a member that leaves the destination and comes back

Fix merged in python/cpython PR #156000 on 2026-08-19 — awaiting tagged release

https://github.com/python/cpython/pull/156000

Vendor Advisories for CVE-2026-19672(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 5× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 17:39 UTCGHSA enrichment
  3. 2026-08-19 16:24 UTCEG score recompute
  4. 2026-08-19 15:38 UTCEG score recompute
  5. 2026-08-19 15:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19672?
CVE-2026-19672 is a medium vulnerability published on August 19, 2026. The tarfile module's tar and data extraction filters created directories outside the destination for members whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The containment check used the resolved path, but intermediate directories were created from the name…
When was CVE-2026-19672 disclosed?
CVE-2026-19672 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19672 actively exploited?
CVE-2026-19672 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 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-19672?
CVE-2026-19672 has a CVSS v3 base score of 6.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-19672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19672, 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-19672

Explore →

Is Your Infrastructure Affected by CVE-2026-19672?

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