Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-11816 high CVSS 8.1

Path Traversal in keras (CVE-2026-11816)

Summary

Path traversal in keras (CVE-2026-11816). Confidential information can be exposed externally. Exploitable via AttributeError. Mitigation: upgrade to 3.14.0 or later.

Original description

The description as published by the source.

Keras versions prior to 3.14.0 are vulnerable to a path traversal issue in the archive extraction utilities located in keras/src/utils/file_utils.py. The functions filter_safe_tarinfos() and filter_safe_zipinfos() validate archive member paths against the process current working directory (CWD) instead of the actual extraction destination. When the process runs with CWD set to /, which is common in Docker containers, CI/CD runners, and Jupyter environments, the validation boundary becomes the filesystem root, allowing traversal paths to bypass the security check. Additionally, the zip filter contains a bug that causes an AttributeError when a blocked entry is encountered, leading to incomplete extraction. Furthermore, Python 3.11 installations lack the filter="data" safety net, leaving them entirely reliant on the flawed CWD-based filter. Exploitation of this vulnerability can result in arbitrary file writes outside the intended extraction directory, enabling attackers to overwrite configuration files, inject malicious code, or corrupt machine learning datasets and pipelines.

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-11816 has been found in keras.
Attackers can target a specific entry point like AttributeError over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade keras to 3.14.0 or later.
If unsure, ask your IT team or search "keras CVE-2026-11816" on the vendor's site.

CVE-2026-11816 (keras) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: AttributeError
Patched: 3.14.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

Path traversal (CWE-22) exists in keras. Attackers reach the vulnerable code path via AttributeError without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of keras. Attack surface: AttributeError.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.14.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

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. 2
    Apply patch patch 
    Upgrade keras to 3.14.0

    ステージング環境で 3.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details