CVE-2025-12060

HIGHNVD 8.98.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.9 under NVD CVSS v3. EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
8.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The keras.utils.get_file API in Keras, when used with the extract=True option for tar archives, is vulnerable to a path traversal attack. The utility uses Python's tarfile.extractall function without the filter="data" feature. A remote attacker can craft a malicious tar archive containing special symlinks, which, when extracted, allows them to write arbitrary files to any location on the filesystem outside of the intended destination folder. This vulnerability is linked to the underlying Python tarfile weakness, identified as CVE-2025-4517. Note that upgrading Python to one of the versions that fix CVE-2025-4517 (e.g. Python 3.13.4) is not enough. One additionally needs to upgrade Keras to a version with the fix (Keras 3.12).

CVSS v3
8.9
EG Score
8.9HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity89% × 45%
The EG Score, 8.9 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2025

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated Jul 26, 2026
Patch available. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

`keras.utils.get_file` Directory Traversal Vulnerability for TAR files · Advisory · keras-team/keras · GitHub

https://github.com/keras-team/keras/security/advisories/GHSA-hjqc-jx6g-rwp9
GitHub pull request Patch Available

Use `filter="data"` option of `TarFile.extractall`.

Patch available: keras-team/keras v3.12.0 (PR #21760 merged 2025-10-21)

https://github.com/keras-team/keras/pull/21760

Patch Availability(3)

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

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
keras0.2.0 ... 3.9.2 (112 versions)
  • every version up to 3.12.0: fixed in 3.12.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-12 17:26 UTCEG score recompute
  3. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-11 20:56 UTCEG score recompute
  5. 2026-10-11 19:06 UTCEG score recompute
  6. 2026-10-11 15:47 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-10 16:55 UTCOSV refresh
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-09-21 03:49 UTCOSV refresh
  25. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 66 more
  1. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-09-02 01:41 UTCOSV refresh
  17. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  25. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  26. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  27. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  28. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  29. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  30. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  31. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  32. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  33. 2026-08-16 05:05 UTCOSV refresh
  34. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  35. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  36. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  37. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  38. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  40. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  41. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  42. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  44. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  45. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  46. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  47. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  48. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  49. 2026-07-31 22:12 UTCOSV refresh
  50. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  51. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  52. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  53. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  54. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  55. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  56. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  57. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  58. 2026-07-23 02:48 UTCEG score recompute
  59. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  60. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  61. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  62. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  63. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  64. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  65. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  66. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile

Frequently asked(5)

What is CVE-2025-12060?
CVE-2025-12060 is a high-severity vulnerability; its CVE record was published on October 30, 2025. The keras.utils.get_file API in Keras, when used with the extract=True option for tar archives, is vulnerable to a path traversal attack. The utility uses Python's tarfile.extractall function without the filter="data" feature. A remote attacker can craft a malicious tar archive containing special…
When was the CVE record for CVE-2025-12060 published?
The CVE record for CVE-2025-12060 was published on October 30, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-12060 actively exploited?
CVE-2025-12060 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-12060?
CVE-2025-12060 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2025-12060?
A fix for CVE-2025-12060 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-12060 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-12060

Explore →

Is Your Infrastructure Affected by CVE-2025-12060?

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