CVE-2026-12570

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

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

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.5(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

September 3, 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
generic

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(1)

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 rangeFixed inDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1——
PyPI(1)
PackageVulnerable rangeFixed inDependents
keras0.2.0 ... 3.9.2 (122 versions)3.15.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 56× 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-09-19 02:49 UTCEG score recompute
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 01:32 UTCEG score recompute
  4. 2026-09-17 00:51 UTCEG score recompute
  5. 2026-09-15 14:08 UTCEG score recompute
  6. 2026-09-14 09:18 UTCEG score recompute
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-13 08:39 UTCEG score recompute
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-12 07:57 UTCEG score recompute
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-11 09:36 UTCEPSS rescore
  13. 2026-09-11 07:15 UTCEG score recompute
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-10 06:36 UTCEG score recompute
  16. 2026-09-09 05:56 UTCEG score recompute
  17. 2026-09-08 22:00 UTCEPSS rescore
  18. 2026-09-07 17:32 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-05 02:15 UTCEG score recompute
  22. 2026-09-03 03:53 UTCEG score recompute
  23. 2026-09-02 14:11 UTCEPSS rescore
  24. 2026-09-01 17:30 UTCEG score recompute
  25. 2026-09-01 17:30 UTCGHSA enrichment
Show 64 more
  1. 2026-09-01 13:53 UTCEPSS rescore
  2. 2026-09-01 04:39 UTCEPSS rescore
  3. 2026-08-31 11:55 UTCEG score recompute
  4. 2026-08-31 11:55 UTCGHSA enrichment
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 10:53 UTCEG score recompute
  7. 2026-08-30 10:53 UTCGHSA enrichment
  8. 2026-08-30 01:21 UTCEPSS rescore
  9. 2026-08-29 10:11 UTCEG score recompute
  10. 2026-08-29 10:11 UTCGHSA enrichment
  11. 2026-08-28 21:40 UTCEPSS rescore
  12. 2026-08-28 05:58 UTCEG score recompute
  13. 2026-08-28 05:57 UTCGHSA enrichment
  14. 2026-08-27 14:24 UTCEPSS rescore
  15. 2026-08-27 05:01 UTCEG score recompute
  16. 2026-08-27 05:01 UTCGHSA enrichment
  17. 2026-08-26 04:22 UTCEG score recompute
  18. 2026-08-26 04:22 UTCGHSA enrichment
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-25 03:40 UTCEG score recompute
  21. 2026-08-25 03:40 UTCGHSA enrichment
  22. 2026-08-24 03:00 UTCGHSA enrichment
  23. 2026-08-23 02:18 UTCEG score recompute
  24. 2026-08-23 02:18 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 01:38 UTCEG score recompute
  27. 2026-08-22 01:38 UTCGHSA enrichment
  28. 2026-08-21 23:48 UTCEPSS rescore
  29. 2026-08-21 00:58 UTCEG score recompute
  30. 2026-08-21 00:58 UTCGHSA enrichment
  31. 2026-08-20 22:55 UTCEPSS rescore
  32. 2026-08-20 00:20 UTCEG score recompute
  33. 2026-08-20 00:20 UTCGHSA enrichment
  34. 2026-08-19 17:03 UTCEPSS rescore
  35. 2026-08-18 23:40 UTCEG score recompute
  36. 2026-08-18 23:40 UTCGHSA enrichment
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-17 23:02 UTCEG score recompute
  39. 2026-08-17 23:02 UTCGHSA enrichment
  40. 2026-08-16 22:22 UTCEG score recompute
  41. 2026-08-16 22:22 UTCGHSA enrichment
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 21:43 UTCEG score recompute
  45. 2026-08-15 21:43 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-14 21:03 UTCEG score recompute
  48. 2026-08-14 21:03 UTCGHSA enrichment
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-13 20:24 UTCGHSA enrichment
  51. 2026-08-12 19:44 UTCEG score recompute
  52. 2026-08-12 19:44 UTCGHSA enrichment
  53. 2026-08-12 13:50 UTCEPSS rescore
  54. 2026-08-11 19:06 UTCEG score recompute
  55. 2026-08-11 19:05 UTCGHSA enrichment
  56. 2026-08-11 13:42 UTCEPSS rescore
  57. 2026-08-10 23:59 UTCEPSS rescore
  58. 2026-08-10 18:26 UTCEG score recompute
  59. 2026-08-10 18:26 UTCGHSA enrichment
  60. 2026-08-10 17:55 UTCEG score recompute
  61. 2026-08-10 17:55 UTCGHSA enrichment
  62. 2026-08-10 07:20 UTCEG score recompute
  63. 2026-08-10 06:41 UTCEG score recompute
  64. 2026-08-10 06:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12570?
CVE-2026-12570 is a medium vulnerability 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.loadmodel() function. The H5IOStore.getitem method in keras/src/saving/savinglib.py does not validate the shape or size of datasets,…
When was CVE-2026-12570 disclosed?
CVE-2026-12570 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12570 actively exploited?
CVE-2026-12570 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-12570?
CVE-2026-12570 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-12570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12570, 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-12570

Explore →

Is Your Infrastructure Affected by CVE-2026-12570?

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

Start Free Scan →Browse All CVEs