Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-12481 critical CVSS 9.8

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.

AI summary snake-internal / snake-material-v2

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 / no user interaction 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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in keras. Attackers reach the vulnerable code path via ``Lambda`` without authentication.
📍 Affected scope
keras — . Attack surface: `Lambda` / `safe_mode` / `None` / `SafeModeScope`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.15.0**.
🛡️ 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

  1. 1
    Identify exposure identify 
    grep -r 'keras' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keras` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade keras to 3.15.0

    ステージング環境で 3.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip keras
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.15.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →