CVE-2025-13462: Python Software Foundation CPython · Unrestricted File Upload
Affects Python Software Foundation CPythonSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low · fixed in 3.15.0a8 : update Python Software Foundation CPython when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.15.0a8, 3.14.4, 3.13.13 +3
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given the low severity and lack of known exploits, immediate action may not be required but monitoring vendor updates is recommended.
Description
The "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to other implementations.
References
- github.com/python/cpython/pull/143934 (opens in a new tab)
- github.com/python/cpython/issues/141707 (opens in a new tab)
- mail.python.org/archives/list/security-announce@python.org/thread/EOMI5I66ZMKQ2INNFT6T7IAIKUGPZYIE/ (opens in a new tab)
- github.com/python/cpython/commit/42d754e34c06e57ad6b8e7f92f32af679912d8ab (opens in a new tab)
- github.com/python/cpython/commit/7ad3093d76a748af55bdb1d2e8aad3638163b017 (opens in a new tab)
- github.com/python/cpython/commit/ae99fe3a33b43e303a05f012815cef60b611a9c7 (opens in a new tab)
- github.com/python/cpython/commit/72dde1016493c52abe857fc4a7bf6c40138b4114 (opens in a new tab)
- github.com/python/cpython/commit/9a23b753552afa28e3a2f4d8863572fc66479406 (opens in a new tab)
- github.com/python/cpython/commit/d10950739a78f54d0718d88fb5a868374603c084 (opens in a new tab)