# CVE-2025-1550: Arbitrary Code Execution via Crafted Keras Config for Model Loading

> Attackers can execute arbitrary code by crafting a malicious Keras model archive, bypassing safe mode restrictions during model loading.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Mar 2025
- **Updated:** 24 Jul 2025
- **Also known as:** AZL-58360, GHSA-48g7-3x6r-xfhp, PYSEC-2025-122, UBUNTU-CVE-2025-1550

## What is CVE-2025-1550?

CVE-2025-1550 is a high-severity code injection vulnerability in Google Keras, published on 11 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Keras Model.load_model function permits arbitrary code execution, even with safe_mode=True, through a manually constructed, malicious .keras archive. By altering the config.json file within the archive, an attacker can specify arbitrary Python modules and functions, along with their arguments, to be loaded and executed during model loading.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-1550?

3 open source packages ship an affected version, including keras. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keras` | PyPI | From 3.0.0 | 3.8.0 |
| `keras` | PyPI | From 3.0.0 | 3.9.0 |
| `keras` | PyPI | From 3.0.0 | 3.9.0 |

Products: Keras Keras.

## How do I fix CVE-2025-1550?

Upgrade keras to a fixed version for your release line: 3.8.0 or 3.9.0.

## Is CVE-2025-1550 being exploited?

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

Public exploit code:

- Keras 2.15 - Remote Code Execution (RCE) (exploitdb)
- https://github.com/ChCh0i/cve-2025-1550 (github_poc): https://github.com/ChCh0i/cve-2025-1550

## Other vulnerabilities in Google 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-2026-1462](https://insights.sbomify.com/CVE-2026-1462/): Safe Mode Bypass 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1550 and fix it if it is affected.

What it is: CVE-2025-1550 is a high-severity code injection vulnerability in Google Keras, published on 11 Mar 2025. It can only be exploited from the same machine or local network, 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-2025-1550 exists.

Affected packages and fixed versions:
- keras (PyPI): affected from 3.0.0; fixed in 3.8.0
- keras (PyPI): affected from 3.0.0; fixed in 3.9.0
- keras (PyPI): affected from 3.0.0; fixed in 3.9.0

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-2025-1550/ (Markdown: https://insights.sbomify.com/CVE-2025-1550/index.md)
```

## Sources

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

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