CVE-2026-7774

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% 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
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.9Exploit: None knownExposed: 0

A fix is available — apply it.

tarfile.data_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() to write files outside the destination directory, subject to the permissions of the extracting process.

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

Published

June 4, 2026

Last Modified

August 13, 2026

Advisory Details (9)

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

oss-security - [CVE-2026-7774] Cpython: tarfile.data_filter path traversal bypass allows writing outside the extraction directory

http://www.openwall.com/lists/oss-security/2026/06/04/9
generic

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

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

gh-149486: tarfile.data_filter: validate written link target

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

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

tarfile.data_filter doesn't handle symlinks with empty names · Issue #149486 · python/cpython · GitHub

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

commit 74cca9a92fb7 (python/cpython)

Fix landed in python/cpython commit 74cca9a92fb7 — awaiting tagged release

https://github.com/python/cpython/commit/74cca9a92fb7d653e404843a56b8bdc7b0afdbbf
github_commit

commit 5cf47a248c35 (python/cpython)

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

https://github.com/python/cpython/commit/5cf47a248c35c375d610b87b2f72fd1ed454b558
github_commit

commit 578411982c16 (python/cpython)

Fix landed in python/cpython commit 578411982c16 — awaiting tagged release

https://github.com/python/cpython/commit/578411982c16f753f4893532510099ef665117da
github_commit

commit 0d28f5e46e15 (python/cpython)

Fix landed in python/cpython commit 0d28f5e46e15 — awaiting tagged release

https://github.com/python/cpython/commit/0d28f5e46e151718972dfabd91205444d0037b6d
github_commit

commit 0478bd83d82b (python/cpython)

Fix landed in python/cpython commit 0478bd83d82b — awaiting tagged release

https://github.com/python/cpython/commit/0478bd83d82b255e0f29f613367a59d261e7eaa2

Vendor Advisories for CVE-2026-7774(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.12-venv (3.12.3-1ubuntu0.15) @ noble2026-09-14ubuntu

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

(6 across 3 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 (7 versions)3.13.14-1—
python3.143.14.0-1 ... 3.14.5~rc1-1 (23 versions)3.14.6-1—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-2, 3.13.5-2+deb13u1, 3.13.5-2+deb13u23.13.5-2+deb13u3—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—3.14.7-r0—

Weakness Classification(1)

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 9× in last 7d / 43× 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 245 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-7774?
CVE-2026-7774 is a medium vulnerability published on June 4, 2026. tarfile.data_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() to write files outside the…
When was CVE-2026-7774 disclosed?
CVE-2026-7774 was first published in the National Vulnerability Database on June 4, 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-7774 actively exploited?
CVE-2026-7774 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 53.1% of all scored CVEs.
What is the CVSS score of CVE-2026-7774?
CVE-2026-7774 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-7774?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7774, 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-7774

Explore →

Is Your Infrastructure Affected by CVE-2026-7774?

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

Start Free Scan →Browse All CVEs