SECUFOCUSNOW
Home›CVE index›CVE-2026-1462
Review reviewHigh

CVE-2026-1462

keras-team keras-team/keras, Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.3

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.

CVSS
7.8
EPSS
0.40%
33.3% percentile
CISA KEV
Not listed
Published
2026.04.14
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.40%
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
keras-team keras-team/keras, Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.3
Affected versions
>= unspecified < 3.13.2, 3.13.0, >= 2.25 < 2.25.7
Fixed versions
2.25.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that keras-team keras-team/keras, Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.3 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CWE
CWE-502
CVE-2026-1462 — keras-team keras-team/keras, Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.3 | SECUFOCUS NOW