LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-73: File access and web shell behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1669 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NGoogle
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

7.1High
CVSS 4.0 vector shape for CVE-2026-1669Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPkeras: Keras: Information disclosure via arbitrary file read in model loading mechanism
other:Red Hat severity ratingcvssV3_1
  • 2026-02-11T23:00:48.085Z: Reported to Red Hat.
  • 2026-02-11T22:10:10.031Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleKeras3.0.0unaffected
Weakness

CWE details

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.

CWE-73 · source CWE mapping

External Control of File Name or Path

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.