CVE-2025-4435
published 2025-06-03CVE-2025-4435: 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…
PriorityP341high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
0.47%
37.9th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | jython | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| debian | pypy3 | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| debian | python2.7 | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| debian | python3.11 | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| debian | python3.13 | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| debian | python3.9 | < pypy3 7.3.20+dfsg-2 (forky) | pypy3 7.3.20+dfsg-2 (forky) |
| msrc | azl3_python3_3.12.9-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_tensorflow_2.16.1-9_on_azure_linux_3.0 | — | — |
| msrc | cbl2_python3_3.9.19-14_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python3_3.9.19-15_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python3_3.9.19-16_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python3_3.9.19-17_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python3_3.9.19-18_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python3_3.9.19-19_on_cbl_mariner_2.0 | — | — |
| python_software_foundation | cpython | < 3.10.18 | 3.10.18 |
| python_software_foundation | cpython | >= 3.11.0 < 3.11.13 | 3.11.13 |
| python_software_foundation | cpython | >= 3.12.0 < 3.12.11 | 3.12.11 |
| python_software_foundation | cpython | >= 3.13.0 < 3.13.4 | 3.13.4 |
| python_software_foundation | cpython | >= 3.14.0a1 < 3.14.0b3 | 3.14.0b3 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
osv7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
vendor_msrc6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2025-4435: When using a TarFile
osv·2025-06-03·CVSS 7.5
CVE-2025-4435 [HIGH] CVE-2025-4435: When using a TarFile
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.
GHSA
GHSA-p72v-37h5-753v: When using a TarFile
ghsa_unreviewed·2025-06-03
CVE-2025-4435 [HIGH] CWE-682 GHSA-p72v-37h5-753v: When using a TarFile
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.
Ubuntu
Python vulnerabilities
vendor_ubuntu·2025-06-19
CVE-2025-4517 Python vulnerabilities
Title: Python vulnerabilities
Summary: Python could be made to overwrite files.
It was discovered that Python incorrectly handled tar archive extraction
with the filtering option. An attacker could possibly use this issue to
modify files in arbitrary filesystem locations and cause data loss.
Instructions: In general, a standard system update will make all the necessary changes.
Microsoft
Tarfile extracts filtered members when errorlevel=0
vendor_msrc·2025-06-10·CVSS 6.5
CVE-2025-4435 [HIGH] CWE-682 Tarfile extracts filtered members when errorlevel=0
Tarfile extracts filtered members when errorlevel=0
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
PSF: PSF
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.microso
Red Hat
cpython: Tarfile extracts filtered members when errorlevel=0
vendor_redhat·2025-06-03·CVSS 7.5
CVE-2025-4435 [HIGH] CWE-706 cpython: Tarfile extracts filtered members when errorlevel=0
cpython: 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.
A flaw was found in CPython's tarfile module. This vulnerability allows unauthorized file extraction via crafted tar archives when TarFile.errorlevel=0, bypassing expected filtering mechanisms.
Statement: The severity of this vulnerability was lowered due to the fact that successful exploitation requires the attacker to convince a privileged user or process to extract a malicious tar file. Since tar file extraction typically occurs in trusted
Red Hat
kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
vendor_redhat·2025-04-01·CVSS 5.5
CVE-2025-21908 [MEDIUM] CWE-667 kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
In the Linux kernel, the following vulnerability has been resolved:
NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
Add PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so
nfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.
Otherwise NFS can deadlock waiting for kcompactd enduced writeback which
recurses back to NFS (which triggers writeback to NFSD via NFS loopback
mount on the same host, NFSD blocks waiting for XFS's call to
__filemap_get_folio):
6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.
{---
[58] "kcompactd0"
[] folio_wait_bit+0xe8/0x200
[] folio_wait_writeback+0x2b/0x80
[] nfs_wb_folio+0x80/0x1b0 [nfs]
[] nfs_release_folio
Debian
CVE-2025-4435: jython - When using a TarFile.errorlevel = 0 and extracting with a filter the documented ...
vendor_debian·2025·CVSS 7.5
CVE-2025-4435 [HIGH] CVE-2025-4435: jython - When using a TarFile.errorlevel = 0 and extracting with a filter the documented ...
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.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
No detection rules found.
Bugzilla
CVE-2025-4435 cpython: Tarfile extracts filtered members when errorlevel=0
bugzilla·2025-06-03·CVSS 7.5
CVE-2025-4435 [HIGH] CVE-2025-4435 cpython: Tarfile extracts filtered members when errorlevel=0
CVE-2025-4435 cpython: 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.
Discussion:
This issue has been addressed in the following products:
Red Hat Enterprise Linux 9.4 Extended Update Support
Via RHSA-2025:9918 https://access.redhat.com/errata/RHSA-2025:9918
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 8
Via RHSA-2025:10026 https://access.redhat.com/errata/RHSA-2025:10026
---
This issue has been addressed in the following products:
Red Hat Enterpri
Bugzilla
CVE-2025-21908 kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
bugzilla·2025-04-01·CVSS 5.5
CVE-2025-21908 [MEDIUM] CVE-2025-21908 kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
CVE-2025-21908 kernel: NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
In the Linux kernel, the following vulnerability has been resolved:
NFS: fix nfs_release_folio() to not deadlock via kcompactd writeback
Add PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so
nfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.
Otherwise NFS can deadlock waiting for kcompactd enduced writeback which
recurses back to NFS (which triggers writeback to NFSD via NFS loopback
mount on the same host, NFSD blocks waiting for XFS's call to
__filemap_get_folio):
6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.
{---
[58] "kcompactd0"
[] folio_wait_bit+0xe8/0x200
[] folio_wait_writeback+0x2b/0x80
[] nfs_wb_folio+0x80/0x1b0 [nfs]
https://github.com/python/cpython/commit/19de092debb3d7e832e5672cc2f7b788d35951dahttps://github.com/python/cpython/commit/28463dba112af719df1e8b0391c46787ad756dd9https://github.com/python/cpython/commit/3612d8f51741b11f36f8fb0494d79086bac9390ahttps://github.com/python/cpython/commit/4633f3f497b1ff70e4a35b6fe2c907cbe2d4cb2ehttps://github.com/python/cpython/commit/9c1110ef6652687d7c55f590f909720eddde965ahttps://github.com/python/cpython/commit/9e0ac76d96cf80b49055f6d6b9a6763fb9215c2ahttps://github.com/python/cpython/commit/aa9eb5f757ceff461e6e996f12c89e5d9b583b01https://github.com/python/cpython/commit/dd8f187d0746da151e0025c51680979ac5b4cfb1https://github.com/python/cpython/issues/135034https://github.com/python/cpython/pull/135037https://mail.python.org/archives/list/[email protected]/thread/MAXIJJCUUMCL7ATZNDVEGGHUMQMUUKLG/
2025-06-03
Published