Vulnerability in keras (CVE-2026-12480)
Summary
Vulnerability in keras (CVE-2026-12480). Confidential information can be exposed externally. Exploitable via file_editor.py. Mitigation: upgrade to 3.15.0 or later.
Original description
The description as published by the source.
Keras versions up to and including 3.13.2 are vulnerable to an arbitrary HDF5 file read due to an incomplete fix for CVE-2026-1669. The vulnerability resides in the H5IOStore._verify_dataset() and file_editor.py methods, which fail to check the dataset.is_virtual property of HDF5 datasets. This allows an attacker to craft a malicious .keras model archive or .h5 weights file containing a Virtual Dataset (VDS) that references external HDF5 files on the victim's filesystem. When the victim loads the model using keras.models.load_model() or keras.saving.load_model(), the external file is transparently read, leading to potential information disclosure. Fixed in versions 3.12.3 and 3.15.0.
Source: GitHub Security Advisories (Global) 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-12480 has been found in keras.
Attackers can target a specific entry point like file_editor.py over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade keras to 3.15.0 or later.
If unsure, ask your IT team or search "keras CVE-2026-12480" on the vendor's site.
CVE-2026-12480 (keras) — CWE-73 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: file_editor.py / dataset.is_virtual
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.
A vulnerability (CWE-73) exists in keras. Attackers reach the vulnerable code path via file_editor.py without authentication.
Check the vendor advisory for the affected versions of keras. Attack surface: file_editor.py / dataset.is_virtual.
Severity: Medium (CVSS 5.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
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web huntr.com
- web github.com
- web github.com
- web github.com