CVE-2026-82049

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

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

In CPython 3.13 and earlier, the tarfile module's data and tar extraction filters are vulnerable to crafted archives containing a hard link to a symbolic link. Such archives may cause extraction to modify the permissions or modification time of a file outside the destination directory, or expose the contents of that file within the extracted tree.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Mailman 3 [CVE-2026-82049] tarfile extraction filters allow file modification and content disclosure via hard link to symlink - Security-announce - python.org

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

gh-157190: Follow symlinks when extracting `tarfile` hard links

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

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

tarfile `data`/`tar` filter bypass via hard link to a symlink · Issue #157190 · python/cpython · GitHub

https://github.com/python/cpython/issues/157190
github_commit

commit 5a57248b22ad (python/cpython)

Fix landed in python/cpython commit 5a57248b22ad — awaiting tagged release

https://github.com/python/cpython/commit/5a57248b22ad3b9aafcaaadae2c304a1923daeca

Vendor Advisories for CVE-2026-82049(1)

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 36× in last 7d / 36× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 13:30 UTCVendor advisory
  3. 2026-09-20 13:30 UTCGHSA enrichment
  4. 2026-09-20 00:42 UTCEG score recompute
  5. 2026-09-20 00:42 UTCVendor advisory
  6. 2026-09-20 00:42 UTCGHSA enrichment
  7. 2026-09-19 11:55 UTCVendor advisory
  8. 2026-09-19 11:55 UTCGHSA enrichment
  9. 2026-09-18 23:08 UTCEG score recompute
  10. 2026-09-18 23:08 UTCVendor advisory
  11. 2026-09-18 23:08 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 10:21 UTCVendor advisory
  14. 2026-09-18 10:21 UTCGHSA enrichment
  15. 2026-09-17 21:34 UTCEG score recompute
  16. 2026-09-17 21:34 UTCVendor advisory
  17. 2026-09-17 21:34 UTCGHSA enrichment
  18. 2026-09-17 08:46 UTCVendor advisory
  19. 2026-09-17 08:46 UTCGHSA enrichment
  20. 2026-09-16 19:58 UTCGHSA enrichment
  21. 2026-09-16 17:56 UTCEG score recompute
  22. 2026-09-16 17:56 UTCGHSA enrichment
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-16 04:27 UTCGHSA enrichment
Show 11 more
  1. 2026-09-16 03:01 UTCGHSA enrichment
  2. 2026-09-15 14:14 UTCGHSA enrichment
  3. 2026-09-15 01:27 UTCEG score recompute
  4. 2026-09-15 01:27 UTCGHSA enrichment
  5. 2026-09-15 00:45 UTCEG score recompute
  6. 2026-09-15 00:45 UTCGHSA enrichment
  7. 2026-09-14 20:23 UTCEG score recompute
  8. 2026-09-14 19:50 UTCEG score recompute
  9. 2026-09-14 19:30 UTCEG score recompute
  10. 2026-09-14 19:19 UTCEG score recompute
  11. 2026-09-14 19:18 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82049?
CVE-2026-82049 is a high vulnerability published on September 14, 2026. In CPython 3.13 and earlier, the tarfile module's data and tar extraction filters are vulnerable to crafted archives containing a hard link to a symbolic link. Such archives may cause extraction to modify the permissions or modification time of a file outside the destination directory, or expose…
When was CVE-2026-82049 disclosed?
CVE-2026-82049 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82049 actively exploited?
CVE-2026-82049 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 92.0% of all scored CVEs.
What is the CVSS score of CVE-2026-82049?
CVE-2026-82049 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-82049?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82049, 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-82049

Explore →

Is Your Infrastructure Affected by CVE-2026-82049?

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

Start Free Scan →Browse All CVEs