CVE-2026-4360

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM 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 — 4 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

A fix is available — apply it.

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(medium)
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
20%
KEV
Not listed

Published

June 30, 2026

Last Modified

August 13, 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(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.9-venv (3.9.5-3ubuntu0~20.04.1+esm11) @ focal2026-09-18ubuntu
redhatpython3-13-main-3.13.15-1.hum12026-08-13redhat
redhatpython3-14-main-3.14.7-1.hum12026-08-13redhat
redhatpython3-11-main-3.11.15-5.4.hum12026-07-29redhat
redhatpython3-13-main-3.13.14-1.6.hum12026-07-29redhat
redhatpython3-14-main-3.14.6-2.1.hum12026-07-29redhat
redhatpython3-12-main-3.12.13-3.7.hum12026-07-29redhat
redhatpython3-10-main-3.10.20-3.1.hum12026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 6 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (8 versions)3.13.15-1—
python3.143.14.0-1 ... 3.14.6-1 (24 versions)3.14.7-1—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (13 versions)——
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
python3—3.12.14-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—3.14.7-r0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× 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.

Showing the most recent 100 of 204 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:49 UTCEG score recompute
  3. 2026-09-18 06:49 UTCVendor advisory
  4. 2026-09-18 06:49 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-13 13:09 UTCVendor advisory
  9. 2026-09-13 13:09 UTCGHSA enrichment
  10. 2026-09-12 15:10 UTCEG score recompute
  11. 2026-09-12 15:10 UTCVendor advisory
  12. 2026-09-12 15:10 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 14:36 UTCEG score recompute
  18. 2026-09-06 14:36 UTCVendor advisory
  19. 2026-09-06 14:36 UTCGHSA enrichment
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-04 05:06 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 18:07 UTCEG score recompute
  2. 2026-08-30 18:07 UTCVendor advisory
  3. 2026-08-30 18:07 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 22:41 UTCEG score recompute
  7. 2026-08-27 22:41 UTCVendor advisory
  8. 2026-08-27 22:41 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 02:46 UTCEG score recompute
  13. 2026-08-25 02:46 UTCVendor advisory
  14. 2026-08-25 02:46 UTCGHSA enrichment
  15. 2026-08-24 04:46 UTCVendor advisory
  16. 2026-08-24 04:46 UTCGHSA enrichment
  17. 2026-08-23 06:46 UTCEG score recompute
  18. 2026-08-23 06:46 UTCVendor advisory
  19. 2026-08-23 06:46 UTCGHSA enrichment
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-22 08:23 UTCEG score recompute
  22. 2026-08-22 08:23 UTCVendor advisory
  23. 2026-08-22 08:23 UTCGHSA enrichment
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 04:50 UTCEG score recompute
  26. 2026-08-21 04:50 UTCVendor advisory
  27. 2026-08-21 04:50 UTCGHSA enrichment
  28. 2026-08-20 22:55 UTCEPSS rescore
  29. 2026-08-20 05:35 UTCEG score recompute
  30. 2026-08-20 05:35 UTCVendor advisory
  31. 2026-08-20 05:35 UTCGHSA enrichment
  32. 2026-08-19 17:04 UTCEPSS rescore
  33. 2026-08-18 23:04 UTCEG score recompute
  34. 2026-08-18 23:04 UTCVendor advisory
  35. 2026-08-18 23:04 UTCGHSA enrichment
  36. 2026-08-18 13:48 UTCEPSS rescore
  37. 2026-08-17 15:25 UTCEG score recompute
  38. 2026-08-17 15:25 UTCVendor advisory
  39. 2026-08-17 15:25 UTCGHSA enrichment
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-16 17:26 UTCEG score recompute
  42. 2026-08-16 17:26 UTCVendor advisory
  43. 2026-08-16 17:26 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 02:14 UTCEPSS rescore
  46. 2026-08-15 19:22 UTCEG score recompute
  47. 2026-08-15 19:22 UTCVendor advisory
  48. 2026-08-15 19:22 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 21:22 UTCVendor advisory
  51. 2026-08-14 21:22 UTCGHSA enrichment
  52. 2026-08-13 23:22 UTCEG score recompute
  53. 2026-08-13 23:22 UTCVendor advisory
  54. 2026-08-13 23:22 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 01:23 UTCVendor advisory
  57. 2026-08-13 01:23 UTCGHSA enrichment
  58. 2026-08-13 00:41 UTCEG score recompute
  59. 2026-08-13 00:41 UTCVendor advisory
  60. 2026-08-13 00:41 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 11:16 UTCEG score recompute
  63. 2026-08-12 11:16 UTCVendor advisory
  64. 2026-08-12 11:16 UTCGHSA enrichment
  65. 2026-08-11 13:16 UTCEG score recompute
  66. 2026-08-11 13:16 UTCVendor advisory
  67. 2026-08-11 13:16 UTCGHSA enrichment
  68. 2026-08-11 00:00 UTCEPSS rescore
  69. 2026-08-10 15:17 UTCVendor advisory
  70. 2026-08-10 15:17 UTCGHSA enrichment
  71. 2026-08-09 17:18 UTCEG score recompute
  72. 2026-08-09 17:18 UTCVendor advisory
  73. 2026-08-09 17:18 UTCGHSA enrichment
  74. 2026-08-09 13:46 UTCEPSS rescore
  75. 2026-08-08 19:19 UTCEG score recompute

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 August 13, 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 79.6% 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

See which npm, PyPI, Go, and Maven packages are affected by 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