← Back
CVE-2026-1462
high
CVSS 7.8
Unsafe Deserialization in keras (CVE-2026-1462)
Summary
vulnerability in keras (CVE-2026-1462). Successful exploitation can lead to full system takeover. Exploitable via ``TFSMLayer``. Mitigation: upgrade to `3.13.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-1462** has been found in keras.
Attackers can target a specific entry point like ``TFSMLayer`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade keras to **3.13.2** or later.
If unsure, ask your IT team or search "keras CVE-2026-1462" on the vendor's site.
CVE-2026-1462 (keras) — CWE-502 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: `TFSMLayer` / `keras` / `safe_mode`
Patched: `3.13.2` — 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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in keras. Attackers reach the vulnerable code path via ``TFSMLayer`` without authentication.
📍 Affected scope
keras — . Attack surface: `TFSMLayer` / `keras` / `safe_mode`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.13.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade keras to 3.13.2ステージング環境で 3.13.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
keras
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1462
- advisory 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- advisory 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- advisory 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- advisory 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- exploit [email protected]
- package https://github.com/keras-team/keras
- patch [email protected]
- web https://github.com/keras-team/keras/pull/22035