INCIDENT MAP

Browse / Unsafe Model Loading and Supply Chain / CVE-2025-9906

Keras is vulnerable to Deserialization of Untrusted Data

CVE-2025-9906 · 2025-09-19 high

Class
Unsafe Model Loading and Supply Chain (filed by a model that read the advisory)
Technique
Unsafe deserialisation
Affected
keras (PyPI)
Gets past
Safe model loader or scanner
CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

A crafted .keras archive re-enables unsafe deserialisation from inside its config before layer parsing, then a pickled Lambda layer runs attacker code when the model loads. (Our summary, written by a model. The source text is below.)

Details

Arbitrary Code Execution in Keras

Keras versions prior to 3.11.0 allow for arbitrary code execution when loading a crafted .keras model archive, even when safe_mode=True.

The issue arises because the archive’s config.json is parsed before layer deserialization. This can invoke keras.config.enable_unsafe_deserialization(), effectively disabling safe mode from within the loading process itself. An attacker can place this call first in the archive and then include a Lambda layer whose function is deserialized from a pickle, leading to the execution of attacker-controlled Python code as soon as a victim loads the model file.

Exploitation requires a user to open an untrusted model; no additional privileges are needed. The fix in version 3.11.0 enforces safe-mode semantics *before* reading any user-controlled configuration and prevents the toggling of unsafe deserialization via the config file.

Affected versions: < 3.11.0
Patched version: 3.11.0

It is recommended to upgrade to version 3.11.0 or later and to avoid opening untrusted model files.

References

Source: GitHub Advisory Database, used under CC BY 4.0.