# CVE-2026-1462: Safe Mode Bypass in keras-team/keras

> Attackers can execute arbitrary code by bypassing safe mode during the deserialization of Keras models containing malicious TensorFlow SavedModels.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-1462, GHSA-4f3f-g24h-fr8m, MINI-j2mx-xh6r-256r, PYSEC-2026-2547, UBUNTU-CVE-2026-1462

## What is CVE-2026-1462?

CVE-2026-1462 is a high-severity unsafe deserialization vulnerability in keras-team/keras, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the `TFSMLayer` class of the `keras` package, version 3.13.0, allows attacker-controlled TensorFlow SavedModels to be loaded during deserialization of `.keras` models, even when `safe_mode=True`. This bypasses the security guarantees of `safe_mode` and enables arbitrary attacker-controlled code execution during model inference under the victim's privileges. The issue arises due to the unconditional loading of external SavedModels, serialization of attacker-controlled file paths, and the lack of validation in the `from_config()` method.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-1462?

3 open source packages ship an affected version, including keras. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keras` | PyPI | All versions | 3.13.2 |
| `keras` | PyPI | All versions | 3.13.2 |
| `keras` | PyPI | All versions | 3.13.2 |

Products: Keras Keras, Redhat Openshift Ai.

## How do I fix CVE-2026-1462?

Upgrade keras to 3.13.2 or later.

## Is CVE-2026-1462 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1462 exists.

## Other vulnerabilities in keras-team/keras

- [CVE-2024-3660](https://insights.sbomify.com/CVE-2024-3660/): Arbitrary code injection vulnerability in Keras framework < 2.13 (critical 9.8)
- [CVE-2026-12481](https://insights.sbomify.com/CVE-2026-12481/): Deserialization of Untrusted Data in keras-team/keras (high 8.8)
- [CVE-2025-9906](https://insights.sbomify.com/CVE-2025-9906/): Arbitrary Code execution in Keras Safe Mode (high 8.6)
- [CVE-2025-8747](https://insights.sbomify.com/CVE-2025-8747/): Keras safe_mode bypass allows arbitrary code execution when loading a malicious model. (high 8.6)
- [CVE-2026-11816](https://insights.sbomify.com/CVE-2026-11816/): Path Traversal in keras-team/keras (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1462 and fix it if it is affected.

What it is: CVE-2026-1462 is a high-severity unsafe deserialization vulnerability in keras-team/keras, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1462 exists.

Affected packages and fixed versions:
- keras (PyPI): affected all versions; fixed in 3.13.2
- keras (PyPI): affected all versions; fixed in 3.13.2
- keras (PyPI): affected all versions; fixed in 3.13.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1462/ (Markdown: https://insights.sbomify.com/CVE-2026-1462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1462
- OSV: https://osv.dev/vulnerability/CVE-2026-1462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1462/
Summaries are generated and may contain mistakes; the official description above is the record.