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.
CVE-2026-4360
LOWPre-NVD 2.02.0—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
2.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.0Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.0
- EG Score
- 2.0(medium)
- EPSS
- 22.2%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 1, 2026
References (7)
- cna@pythonhttps://github.com/python/cpython/commit/5e0ef3f1afe892e4f64eb83368db57ac4c40cba0
- cna@pythonhttps://github.com/python/cpython/commit/7b57e8d51446297b8c7c482d224bc5f1938e4301
- cna@pythonhttps://github.com/python/cpython/commit/7ccdbaba2c54250a70d7f25632152df7655a5e0a
- cna@pythonhttps://github.com/python/cpython/commit/eee3ddf0ca10283cc7fea724aae9cd8665f8d15e
- cna@pythonhttps://github.com/python/cpython/issues/151987
- cna@pythonhttps://github.com/python/cpython/pull/151988
- cna@pythonhttps://mail.python.org/archives/list/[email protected]/thread/TWZW2PC2AZOV6FENIHFSRC63OM7MBGSB/
Vendor Advisories for CVE-2026-4360(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:10 UTCEG score recompute
- 2026-07-06 16:10 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 16:20 UTCEG score recompute
- 2026-07-03 16:20 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 16:34 UTCEG score recompute▲ 2.00
- 2026-06-30 16:34 UTCGHSA enrichment
- 2026-06-30 16:32 UTCNVD updateCVSS v3 → 2 · CVSS v4 → 2
- 2026-06-30 16:31 UTCEG score recompute
- 2026-06-30 16:31 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-4360?
CVE-2026-4360 is a low vulnerability published on June 30, 2026. 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.
When was CVE-2026-4360 disclosed?
CVE-2026-4360 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4360 actively exploited?
CVE-2026-4360 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4360?
CVE-2026-4360 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-4360?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4360, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-4360
Is Your Infrastructure Affected by CVE-2026-4360?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.