CVE-2026-4360

MEDIUMNVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-06-30. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 23, 2026

Advisory Details (8)

Auto-updated Jul 9, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic
https://mail.python.org/archives/list/[email protected]/thread/TWZW2PC2AZOV6FENIHFSRC63OM7MBGSB/
github_pr

gh-151987: Pass filter_function to TarFile._extract_one() during .extract()

Fix merged in python/cpython PR #151988 on 2026-06-29 — awaiting tagged release

https://github.com/python/cpython/pull/151988
generic

Tarfile.extract doesn't fully respect the filter parameter · Issue #151987 · python/cpython · GitHub

https://github.com/python/cpython/issues/151987
github_commit

commit eee3ddf0ca10 (python/cpython)

Fix landed in python/cpython commit eee3ddf0ca10 — awaiting tagged release

https://github.com/python/cpython/commit/eee3ddf0ca10283cc7fea724aae9cd8665f8d15e
github_commit

commit d2b2f5eacab4 (python/cpython)

Fix landed in python/cpython commit d2b2f5eacab4 — awaiting tagged release

https://github.com/python/cpython/commit/d2b2f5eacab4dd48446b63340613b05dcbbf0b44
github_commit

commit 7ccdbaba2c54 (python/cpython)

Fix landed in python/cpython commit 7ccdbaba2c54 — awaiting tagged release

https://github.com/python/cpython/commit/7ccdbaba2c54250a70d7f25632152df7655a5e0a
github_commit

commit 7b57e8d51446 (python/cpython)

Fix landed in python/cpython commit 7b57e8d51446 — awaiting tagged release

https://github.com/python/cpython/commit/7b57e8d51446297b8c7c482d224bc5f1938e4301
github_commit

commit 5e0ef3f1afe8 (python/cpython)

Fix landed in python/cpython commit 5e0ef3f1afe8 — awaiting tagged release

https://github.com/python/cpython/commit/5e0ef3f1afe892e4f64eb83368db57ac4c40cba0

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 13× in last 7d / 53× 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.

  1. 2026-07-28 01:09 UTCEG score recompute
  2. 2026-07-28 01:09 UTCGHSA enrichment
  3. 2026-07-27 03:10 UTCEG score recompute
  4. 2026-07-27 03:10 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 05:11 UTCEG score recompute
  7. 2026-07-26 05:10 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:14 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:25 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 23:55 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-16 01:56 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 03:56 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 28 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 05:57 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 07:58 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 09:59 UTCGHSA enrichment
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 11:59 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 14:00 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 15:59 UTCEG score recompute▲ 3.30
  13. 2026-07-09 15:59 UTCGHSA enrichment
  14. 2026-07-09 02:56 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:10 UTCGHSA enrichment
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-03 16:20 UTCGHSA enrichment
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-06-30 16:34 UTCEG score recompute▲ 2.00
  25. 2026-06-30 16:34 UTCGHSA enrichment
  26. 2026-06-30 16:32 UTCNVD updateCVSS v3 → 2 · CVSS v4 → 2
  27. 2026-06-30 16:31 UTCEG score recompute
  28. 2026-06-30 16:31 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4360?
CVE-2026-4360 is a medium 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 23, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-4360?
CVE-2026-4360 has a CVSS v3 base score of 5.3 (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

Explore →

Is Your Infrastructure Affected by CVE-2026-4360?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs