Path Traversal in keras (CVE-2026-9335)
Summary
Path traversal in keras (CVE-2026-9335). Confidential information can be exposed externally. Exploitable via KerasFileEditor. Mitigation: upgrade to 3.15.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9335 has been found in keras.
Attackers can target a specific entry point like KerasFileEditor over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade keras to 3.15.0 or later.
If unsure, ask your IT team or search "keras CVE-2026-9335" on the vendor's site.
CVE-2026-9335 (keras) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: KerasFileEditor / keras.saving.load_weights / safe_get_h5_group / safe_get_h5_dataset
Patched: 3.15.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in keras. Attackers reach the vulnerable code path via KerasFileEditor without authentication.
Check the vendor advisory for the affected versions of keras. Attack surface: KerasFileEditor / keras.saving.load_weights / safe_get_h5_group / safe_get_h5_dataset.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 3.15.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'keras' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'keras' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
kerasを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade keras to 3.15.0ステージング環境で 3.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-9335 keras
- Ubuntu UBUNTU-CVE-2026-9335 keras
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web huntr.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com