CVE-2026-4360
CVE-2026-4360 — Tarfile.extract() doesn't fully respect filter parameter
In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract() function.
Published Updated Sources: cvelistV5, PSF
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
2
LOW
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 2 | CVSS 4.0 | LOW | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-281
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /gid.
References
10 on the record
- mail.python.org/archives/list/[email protected]/thread/TWZW2PC2AZOV6FENIHFSRC63OM7MBGSB/
vendor-advisory
- github.com/python/cpython/pull/151988
patch
- github.com/python/cpython/issues/151987
issue-tracking
- github.com/python/cpython/commit/5e0ef3f1afe892e4f64eb83368db57ac4c40cba0
patch
- github.com/python/cpython/commit/7b57e8d51446297b8c7c482d224bc5f1938e4301
patch
- github.com/python/cpython/commit/7ccdbaba2c54250a70d7f25632152df7655a5e0a
patch
- github.com/python/cpython/commit/eee3ddf0ca10283cc7fea724aae9cd8665f8d15e
patch
- github.com/python/cpython/commit/d2b2f5eacab4dd48446b63340613b05dcbbf0b44
patch
Elsewhere on this site
- python software foundationevery CVE for this vendor
- CWE-281other pages naming this weakness
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 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.