CVE-2026-0897

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling in the HDF5 weight loading component in Google Keras 3.0.0 through 3.13.0 on all platforms allows a remote attacker to cause a Denial of Service (DoS) through memory exhaustion and a crash of the Python interpreter via a crafted .keras archive containing a valid model.weights.h5 file whose dataset declares an extremely large shape.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
21.9%
KEV
Not listed

Published

January 15, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Jul 2, 2026
Patch available. Sources: redhat, github_pr.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-0897.json
redhat

2430027 – (CVE-2026-0897) CVE-2026-0897 Keras: Keras: Denial of Service via crafted HDF5 weight loading file

https://bugzilla.redhat.com/show_bug.cgi?id=2430027
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-0897
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:4271
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3782
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3713
github_pr Patch Available

Fix DoS via malicious HDF5 dataset metadata in KerasFileEditor

Patch available: keras-team/keras v3.14.0 (PR #21880 merged 2025-12-29)

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

Vendor Advisories for CVE-2026-0897(5)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhtas/model-transparency-rhel9:17726146352026-03-11redhat
redhatrhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:17720932722026-03-04redhat
redhatrhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:17715028842026-03-04redhat

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)
PyPI(1)
PackageVulnerable rangeFixed inDependents
keras3.0.0 ... 3.9.2 (32 versions)3.13.1—

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 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-07-19 14:30 UTCEPSS rescore
  2. 2026-07-19 02:28 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-16 17:02 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 02:21 UTCNVD updateCVSS v3 → 7.5
  7. 2026-07-15 02:06 UTCMITRE cvelistV5CVSS v3 → 7.6
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 05:32 UTCOSV refresh
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 52 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-17 17:05 UTCOSV refresh
  19. 2026-06-16 17:52 UTCEPSS rescore
  20. 2026-06-15 17:48 UTCEPSS rescore
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-13 23:00 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-10 22:18 UTCEPSS rescore
  27. 2026-06-10 13:22 UTCEPSS rescore
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 15:24 UTCEPSS rescore
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:47 UTCEPSS rescore
  36. 2026-06-05 06:10 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-04 13:12 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-01 13:51 UTCEPSS rescore
  42. 2026-06-01 13:51 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 00:16 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 15:53 UTCEG score recompute
  50. 2026-05-29 15:53 UTCVendor advisory
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-0897?
CVE-2026-0897 is a high vulnerability published on January 15, 2026. Allocation of Resources Without Limits or Throttling in the HDF5 weight loading component in Google Keras 3.0.0 through 3.13.0 on all platforms allows a remote attacker to cause a Denial of Service (DoS) through memory exhaustion and a crash of the Python interpreter via a crafted .keras archive…
When was CVE-2026-0897 disclosed?
CVE-2026-0897 was first published in the National Vulnerability Database on January 15, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0897 actively exploited?
CVE-2026-0897 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0897?
CVE-2026-0897 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-0897?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0897, 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-0897

Explore →

Is Your Infrastructure Affected by CVE-2026-0897?

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

Start Free Scan →Browse All CVEs