CVE-2026-114583 — tar filter allows writing outside destination via empty-named symlink
tarfile.tar_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() with filter="tar" to write files outside the destination directory, subject to the permissions of the extracting process. This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Python CPython).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | cna@python.org via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | PSF via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: cna@python.org) EPSS over time FIRST
Oct 23, 2026 → Oct 28, 2026 · 6 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products removed · 1
- Affected products added · python software foundation/cpython
- Affected products removed · 1
- Affected products added · python software foundation/cpython
- Source status changed · Received → Awaiting Analysis
- Affected products added · python software foundation/cpython
- Record published
- CVSS changed · 6.9
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 4× References added · Oct 22, 2026 – Oct 25, 2026
- 1× Official description updated · Oct 22, 2026 – Oct 22, 2026
References
12 on the record
- github.com/python/cpython/commit/04d8fca7da2cf3ebc0881fec8a53a1330c3b665d
- github.com/python/cpython/commit/bc93f8ad4c4a0f92d184ec8fccc8ff8a651dcec2
- github.com/python/cpython/commit/f4401da82e2baec5dab06cf070fbca77d53220f0
- github.com/python/cpython/commit/e7e0b3523ad6ba8472873dda594cf4021a16f8b5
- github.com/python/cpython/commit/c6ada40177436e4e2533a7b252082b5f0c043477
- github.com/python/cpython/commit/0901ad4ffb22605f12b705d1c1197f0a01f0ba0b
- github.com/python/cpython/pull/160098
- mail.python.org/archives/list/security-announce@python.org/thread/43JOWPRAV5DI3VZ4FUE
- mail.python.org/archives/list/security-announce@python.org/thread/43JOWPRAV5DI3VZ4FUE
- nvd.nist.gov/vuln/detail/CVE-2026-114583
- github.com/advisories/GHSA-mw29-5qxh-rr87
- github.com/python/cpython/issues/160097
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-116566 socket.getaddrinfo() accepts embedded null bytes in host and port 8h
- Low CVE-2026-103995 Lenient parsing of integers for response body and chunk framing 2d
- Critical CVE-2026-115557 Distrust compromised intermediate certificates in ssl module 5d
- High CVE-2026-19553 SSLContext.wrap_bio() missing validation of server_hostname parameter 29d
- Critical CVE-2026-19445 Use-after-free of a server-side SSLContext when sni_callback switches contexts 29d
- Medium CVE-2026-12345 Race condition in tempfile.TemporaryDirectory cleanup allows deleting files outside the temporary directory Sep 29, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-114583 is "tar filter allows writing outside destination via empty-named symlink", rated Medium. It affects CPython (Python); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.9 describes technical severity. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.