Deserialization of Untrusted Data Affecting py3.11-keras package, versions <3.13.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.06% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-PY311KERAS-16087207
  • published16 Apr 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

NewCVE-2026-1462  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade Minimos:latest py3.11-keras to version 3.13.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream py3.11-keras package and not the py3.11-keras package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.