CVE-2025-4435

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-06-03. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
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.5Exploit: None knownExposed: 0

A fix is available — apply it.

When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not skipped.

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

Published

June 3, 2025

Last Modified

July 31, 2026

Advisory Details (10)

Auto-updated Jul 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
github_commit

commit 9c1110ef6652 (python/cpython)

Fix landed in python/cpython commit 9c1110ef6652 — awaiting tagged release

https://github.com/python/cpython/commit/9c1110ef6652687d7c55f590f909720eddde965a
github_commit

commit 4633f3f497b1 (python/cpython)

Fix landed in python/cpython commit 4633f3f497b1 — awaiting tagged release

https://github.com/python/cpython/commit/4633f3f497b1ff70e4a35b6fe2c907cbe2d4cb2e
github_commit

commit 28463dba112a (python/cpython)

Fix landed in python/cpython commit 28463dba112a — awaiting tagged release

https://github.com/python/cpython/commit/28463dba112af719df1e8b0391c46787ad756dd9
github_commit

commit aa9eb5f757ce (python/cpython)

Fix landed in python/cpython commit aa9eb5f757ce — awaiting tagged release

https://github.com/python/cpython/commit/aa9eb5f757ceff461e6e996f12c89e5d9b583b01
github_commit

commit 19de092debb3 (python/cpython)

Fix landed in python/cpython commit 19de092debb3 — awaiting tagged release

https://github.com/python/cpython/commit/19de092debb3d7e832e5672cc2f7b788d35951da
github_commit

commit 9e0ac76d96cf (python/cpython)

Fix landed in python/cpython commit 9e0ac76d96cf — awaiting tagged release

https://github.com/python/cpython/commit/9e0ac76d96cf80b49055f6d6b9a6763fb9215c2a
github_commit

commit 3612d8f51741 (python/cpython)

Fix landed in python/cpython commit 3612d8f51741 — awaiting tagged release

https://github.com/python/cpython/commit/3612d8f51741b11f36f8fb0494d79086bac9390a
generic

Mailman 3 Multiple CVEs (1 CRITICAL, 3 HIGH, 1 MODERATE) affecting the tarfile module - Security-announce - python.org

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

gh-135034: Normalize link targets in tarfile, add `os.path.realpath(strict='allow_missing')`

Fix merged in python/cpython PR #135037 on 2025-06-03 — awaiting tagged release

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

Multiple tarfile extraction filter bypasses (`filter="tar"`/`filter="data"`) · Issue #135034 · python/cpython · GitHub

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

Vendor Advisories for CVE-2025-4435(14)

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

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.13-venv (3.13.0-1ubuntu0.3) @ oracular2026-05-21ubuntu
redhatpython39-devel:3.9-8100020251126112422.d47b87a42025-12-18redhat
redhatdiscovery/discovery-server-rhel9:2.0.1-17544787272025-08-06redhat
redhatpython3-0:3.6.8-51.el8_8.102025-07-08redhat
redhatpython3-0:3.6.8-47.el8_6.82025-07-07redhat
redhatpython3.9-0:3.9.18-3.el9_4.82025-07-07redhat
redhatpython3.12-0:3.12.9-1.el9_6.12025-07-02redhat
redhatpython3.12-0:3.12.11-1.el8_102025-07-01redhat
redhatpython3.11-0:3.11.13-1.el8_102025-07-01redhat
redhatpython3.9-0:3.9.21-2.el9_6.12025-07-01redhat
redhatpython3.11-0:3.11.11-2.el9_6.12025-07-01redhat
redhatpython3-0:3.6.8-70.el8_102025-07-01redhat
redhatpython3.12-0:3.12.1-4.el9_4.62025-07-01redhat
redhatpython3.12-0:3.12.9-2.el10_0.22025-07-01redhat
redhatpython3.11-0:3.11.7-1.el9_4.82025-06-30redhat

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

(4 across 2 ecosystems)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.13—3.13.4-1—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2, 7.3.20+dfsg-17.3.20+dfsg-2—
python3.13—3.13.4-1—

Weakness Classification(1)

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 7× in last 7d / 30× 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 187 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-4435?
CVE-2025-4435 is a high vulnerability published on June 3, 2025. When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not skipped.
When was CVE-2025-4435 disclosed?
CVE-2025-4435 was first published in the National Vulnerability Database on June 3, 2025, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-4435 actively exploited?
CVE-2025-4435 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 54.0% of all scored CVEs.
What is the CVSS score of CVE-2025-4435?
CVE-2025-4435 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-4435?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-4435, 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-2025-4435

Explore →

Is Your Infrastructure Affected by CVE-2025-4435?

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

Start Free Scan →Browse All CVEs