Unsafe Deserialization in keras (CVE-2026-12481)
Summary
Vulnerability in keras (CVE-2026-12481). Successful exploitation can lead to full system takeover. Exploitable via Lambda. Mitigation: upgrade to 3.15.0 or later.
Original description
The description as published by the source.
A vulnerability in keras-team/keras version 3.14.0 allows for arbitrary code execution due to improper handling of deserialization in the Lambda layer. Specifically, the _raise_for_lambda_deserialization() function fails to enforce the safe-mode guard when safe_mode is set to None, which is the default value when from_config() is called outside of a SafeModeScope context. This logic error conflates None (unset/default-deny) with False (explicitly disabled), bypassing the guard and allowing attacker-controlled marshal bytecode to be deserialized. Affected call sites include keras.layers.deserialize(config), keras.models.clone_model(model), and any direct invocation of Lambda.from_config(config) without an enclosing SafeModeScope(True). This vulnerability can be exploited to achieve arbitrary OS-level code execution in the context of the server or user process.
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-12481 has been found in keras.
Attackers can target a specific entry point like Lambda over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade keras to 3.15.0 or later.
If unsure, ask your IT team or search "keras CVE-2026-12481" on the vendor's site.
CVE-2026-12481 (keras) — CWE-502 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Lambda / safe_mode / None / SafeModeScope
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.
Unsafe deserialization (CWE-502) exists in keras. Attackers reach the vulnerable code path via Lambda without authentication.
Check the vendor advisory for the affected versions of keras. Attack surface: Lambda / safe_mode / None / SafeModeScope.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
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-12481 keras
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- web huntr.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com