CVE-2026-12570

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2026-08-10. A secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-55002 (ENISA EUVD) · GHSA-74m6-m3xx-3vmj (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.2%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability in keras-team/keras versions <= 3.15.0 allows for a denial of service (DoS) attack when loading malicious .keras model files via the keras.models.load_model() function. The H5IOStore.__getitem__ method in keras/src/saving/saving_lib.py does not validate the shape or size of datasets, leading to unbounded memory allocation. A specially crafted .keras file can exploit this flaw to trigger an out-of-memory (OOM) condition, causing the process to be terminated (exit code 137). This issue bypasses the fix for CVE-2026-0897, which only addressed a similar vulnerability in KerasFileEditor. The attack vector includes poisoned models from public repositories or malicious model registries, posing a risk to machine learning pipelines that process untrusted models.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
8th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

August 10, 2026

Last Modified

October 23, 2026

Advisory Details (2)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit.
GitHub commit Patch Available

commit 4933ea4a5b3f (keras-team/keras)

Patch available: keras-team/keras v3.15.0 (contains commit 4933ea4a5b3f)

https://github.com/keras-team/keras/commit/4933ea4a5b3fcc24ceacdc276f5bb5dfbd06756c
Web page

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

https://huntr.com/bounties/a064f475-780a-409a-82f7-678512f27ad8

Vendor Advisories for CVE-2026-12570(2)

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

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 (122 versions)
  • every version up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 100 of 146 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. None are among the latest 100 rows. The 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-12570?
CVE-2026-12570 is a medium-severity vulnerability; its CVE record was published on August 10, 2026. A vulnerability in keras-team/keras versions <= 3.15.0 allows for a denial of service (DoS) attack when loading malicious .keras model files via the keras.models.load_model() function. The H5IOStore.__getitem__ method in keras/src/saving/saving_lib.py does not validate the shape or size of…
When was the CVE record for CVE-2026-12570 published?
The CVE record for CVE-2026-12570 was published on August 10, 2026. 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-12570 actively exploited?
CVE-2026-12570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12570?
CVE-2026-12570 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12570?
A fix for CVE-2026-12570 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12570 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-2026-12570

Explore →

Is Your Infrastructure Affected by CVE-2026-12570?

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

Book a Demo →Browse All CVEs