CVE-2026-1669: Arbitrary File Read in Keras via HDF5 External Datasets
Arbitrary file read in the model loading mechanism (HDF5 integration) in Keras versions 3.0.0 through 3.13.1 on all supported platforms allows a remote attacker to read local files and disclose sensitive information via a crafted .keras model file utilizing HDF5 external dataset references.
Security readout for executives and security teams
Plain-English summary
Keras can be tricked into reading local files when someone loads a malicious .keras model file. This can expose sensitive data available to the loading process. The issue requires user or system interaction with a crafted model file, but the attacker does not need authentication.
Executive priority
Treat this as a high-priority data exposure risk for ML systems that consume outside model files. Urgency is highest where model loading has broad filesystem access or handles customer-supplied artifacts.
Technical view
CVE-2026-1669 affects Keras 3.0.0 through 3.13.1. The HDF5-backed model loading path mishandles external dataset references, enabling arbitrary local file read. CVSS 4.0 is 7.1 high, with network attack vector, low complexity, no privileges, and user interaction required.
Likely exposure
Organizations using Keras to load .keras model artifacts, especially from users, partners, public repositories, CI pipelines, or automated ML workflows, are the likely exposure group.
Exploitation context
The bundle reports no KEV listing and provides no cited evidence of active exploitation. Exploitation depends on a crafted .keras file being loaded by a vulnerable Keras environment.
Researcher notes
The key condition is HDF5 external dataset handling during Keras model load. Sources identify CWE-200 and CWE-73. Remediation detail is incomplete in the provided bundle, so avoid assuming a specific patched release unless vendor guidance confirms it.
Mitigation direction
Do not load untrusted .keras model files in vulnerable Keras environments.
Check official Keras or Google advisory guidance for fixed versions or workarounds.
Isolate model loading with least-privilege file access and sandboxing.
Restrict ML artifact ingestion to trusted, verified sources.
Review automated pipelines that import external model artifacts.
Validation and detection
Inventory Keras installations and identify versions 3.0.0 through 3.13.1.
Find workflows that load .keras artifacts from external or user-controlled sources.
Confirm model-loading services cannot access unnecessary sensitive local files.
Review logs for unexpected loading of externally supplied model files.
Track vendor advisories for patch availability and update status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.