CVE-2025-4435 | Tarfile extracts filtered members when errorlevel=0

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.

Published: 2025-06-03 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4435 is rated Moderate Risk (54.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.54%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-4435

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-30 0.06% 0.54% +0.48%
2 2025-06-09 0.04% 0.06% +0.01%
3 2025-06-04 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4435

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-4435

OS Trackers for CVE-2025-4435

vendor priority summary link
debian unimportant CVE-2025-4435 unimportant priority: Debian including 6 source packages (jython, pypy3, python2.7, python3.11, python3.13, python3.9), 16 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 14, open 2. https://security-tracker.debian.org/tracker/CVE-2025-4435
redhat medium — https://access.redhat.com/security/cve/CVE-2025-4435
suse high CVE-2025-4435 severity important: SUSE including 559 source package names (0.0.17-1.1:libpython3_11-1_0-3.11.13-150600.3.35.1, 0.0.17-1.1:libpython3_6m1_0-3.6.15-150300.10.97.1, …), 2034 product×package rows across 360 product lines (Container bci/kiwi, Container bci/spack, … (360 product lines)): Fixed 1718, Known Affected 226, Known Not Affected 90. https://www.suse.com/security/cve/CVE-2025-4435/
ubuntu medium CVE-2025-4435 medium priority: Ubuntu including 12 source packages (python2.7, python3.10, …), 84 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 51, not-affected 16, needs-triage 10, released 7. https://ubuntu.com/security/CVE-2025-4435

Affected software / configurations for CVE-2025-4435

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4435

URL Tags
https://github.com/python/cpython/commit/19de092debb3d7e832e5672cc2f7b788d35951da
https://github.com/python/cpython/commit/28463dba112af719df1e8b0391c46787ad756dd9
https://github.com/python/cpython/commit/3612d8f51741b11f36f8fb0494d79086bac9390a
https://github.com/python/cpython/commit/4633f3f497b1ff70e4a35b6fe2c907cbe2d4cb2e
https://github.com/python/cpython/commit/9c1110ef6652687d7c55f590f909720eddde965a
https://github.com/python/cpython/commit/9e0ac76d96cf80b49055f6d6b9a6763fb9215c2a
https://github.com/python/cpython/commit/aa9eb5f757ceff461e6e996f12c89e5d9b583b01
https://github.com/python/cpython/commit/dd8f187d0746da151e0025c51680979ac5b4cfb1
https://github.com/python/cpython/issues/135034
https://github.com/python/cpython/pull/135037
https://mail.python.org/archives/list/[email protected]/thread/MAXIJJCUUMCL7ATZNDVEGGHUMQMUUKLG/
cvelogic Threat Intelligence