Advisory

GHSA-36fq-jgmw-4r9c

Also known as: CVE-2025-9906, PYSEC-2025-76

Summary

Keras is vulnerable to Deserialization of Untrusted Data

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-09-19 09:31 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

keras

PyPI · All systems

Affected

  • introduced 0, fixed 3.11.0 (ecosystem)

Fixed versions

3.11.0

Fix

  • Fixed version 3.11.0
    pip install --upgrade keras==3.11.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences