cve.bz

CVE-2026-9335 keras-team keras-team/keras: Path traversal

6.5 mediumEPSS 0.8%Fix available

Medium (6.5) in keras-team keras-team/keras. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in keras 3.12.3, 3.15.0.

On this page
A vulnerability in keras-team/keras versions <= 3.14.0 allows arbitrary local HDF5 file content disclosure due to improper handling of HDF5 ExternalLinks. The `KerasFileEditor` and `keras.saving.load_weights` functions bypass the `safe_get_h5_group` and `safe_get_h5_dataset` helpers, which are designed to reject ExternalLinks and SoftLinks. This results in automatic dereferencing of links to external HDF5 files, enabling attackers to disclose sensitive data from the victim's local filesystem. Specifically, `KerasFileEditor` extracts attributes and datasets from linked files into its internal structures, while `keras.saving.load_weights` loads weights from linked files into the user's model. This issue can be exploited by providing a malicious `.h5`, `.weights.h5`, or `.keras` file containing ExternalLinks.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • keras (PyPI): fixed in 3.12.3, 3.15.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-9335 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9335?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9335?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9335 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • keras-team:keras-team/keras

Versions

From the CNA's record in the CVE List.

ProductAffected
keras-team/kerasbefore 3.12.3, 3.15.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m8wh-29wm-52mvPyPIkeras<3.12.33.12.3
GHSA-m8wh-29wm-52mvPyPIkeras>=3.13.0 <3.15.03.15.0
PYSEC-2026-3633PyPIkeras<3.12.3
>=3.13.0 <3.15.0
3.12.3, 3.15.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11kerasno fix listedDEBIAN-CVE-2026-9335
Ubuntu18.04:LTS, 20.04:LTSkerasno fix listedUBUNTU-CVE-2026-9335

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact for Red Hat environments because exploitation is restricted to local information disclosure and requires an authenticated user or automated pipeline to load an untrusted model file. Under typical deployments, Keras operations run within the security context of the invoking user or container, restricting disclosed file contents to what the executing process is already authorized to read. Because arbitrary code execution and data tampering are not possible through this flaw, system integrity and availability remain unaffected.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-9335.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON