Path Traversal in keras (CVE-2026-12482)
Summary
Path traversal in keras (CVE-2026-12482). Risk of unauthorized operations or information disclosure. Exploitable via filter_safe_tarinfos. 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.12.0 allows an attacker to craft a malicious tar archive that bypasses the filter_safe_tarinfos validation in keras/src/utils/file_utils.py. Specifically, symlink entries are not subjected to the same is_path_in_dir validation as regular file entries, allowing symlinks to be created outside the intended extraction directory. This can lead to symlink-based file read, file overwrite, or directory escape attacks. The issue is particularly impactful on Python 3.10 and 3.11, where filter_safe_tarinfos is the sole defense against tar path traversal. This vulnerability is distinct from CVE-2025-12060 and other previously reported issues.
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-12482 has been found in keras.
Attackers can target a specific entry point like filter_safe_tarinfos over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade keras to 3.15.0 or later.
If unsure, ask your IT team or search "keras CVE-2026-12482" on the vendor's site.
CVE-2026-12482 (keras) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: filter_safe_tarinfos / is_path_in_dir
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.
Path traversal (CWE-22) exists in keras. Attackers reach the vulnerable code path via filter_safe_tarinfos without authentication.
Check the vendor advisory for the affected versions of keras. Attack surface: filter_safe_tarinfos / is_path_in_dir.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
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-12482 keras
- Ubuntu UBUNTU-CVE-2026-12482 keras
References
- advisory nvd.nist.gov
- 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