CVE-2025-12638

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd 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 weekElevated

Also known asEUVD-2025-199871 (ENISA EUVD)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Keras version 3.11.3 is affected by a path traversal vulnerability in the keras.utils.get_file() function when extracting tar archives. The vulnerability arises because the function uses Python's tarfile.extractall() method without the security-critical filter='data' parameter. Although Keras attempts to filter unsafe paths using filter_safe_paths(), this filtering occurs before extraction, and a PATH_MAX symlink resolution bug triggers during extraction. This bug causes symlink resolution to fail due to path length limits, resulting in a security bypass that allows files to be written outside the intended extraction directory. This can lead to arbitrary file writes outside the cache directory, enabling potential system compromise or malicious code execution. The vulnerability affects Keras installations that process tar archives with get_file() and does not affect versions where this extraction method is secured with the appropriate filter parameter.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

November 28, 2025

Last Modified

October 19, 2026

Advisory Details (1)

Auto-updated Aug 8, 2026
Patch available.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/f94f5beb-54d8-4e6a-8bac-86d9aee103f4

Vendor Advisories for CVE-2025-12638(5)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-modelmesh-runtime-adapter-rhel8:17742831912026-03-25redhat
redhatrhtas/model-transparency-rhel9:17726146352026-03-11redhat
redhatrhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:17715028842026-03-04redhat
redhatrhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:v2.25.1-17649611212025-12-17redhat

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

(1 across 1 ecosystem)
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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 97 of 219 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-12638?
CVE-2025-12638 is a high-severity vulnerability; its CVE record was published on November 28, 2025. Keras version 3.11.3 is affected by a path traversal vulnerability in the keras.utils.getfile() function when extracting tar archives. The vulnerability arises because the function uses Python's tarfile.extractall() method without the security-critical filter='data' parameter. Although Keras…
When was the CVE record for CVE-2025-12638 published?
The CVE record for CVE-2025-12638 was published on November 28, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-12638 actively exploited?
CVE-2025-12638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-12638?
CVE-2025-12638 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2025-12638?
A fix for CVE-2025-12638 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-12638 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-12638

Explore →

Is Your Infrastructure Affected by CVE-2025-12638?

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

Book a Demo →Browse All CVEs