CVE-2026-1462
Keras insecure deserialization
- Published13 Apr 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:24977
- https://access.redhat.com/errata/RHSA-2026:37275
- https://access.redhat.com/security/cve/CVE-2026-1462
- https://bugzilla.redhat.com/show_bug.cgi?id=2457856
- https://github.com/keras-team/keras/commit/b6773d3decaef1b05d8e794458e148cb362f163f
- https://huntr.com/bounties/7e78d6f1-6977-4300-b595-e81bdbda331c
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1462.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-1462 being actively exploited?
CVE-2026-1462 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.40%.
How severe is CVE-2026-1462?
CVE-2026-1462 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.40% probability of exploitation.
Which products are affected by CVE-2026-1462?
Affected products include Keras, Redhat Openshift Ai.
How do I fix CVE-2026-1462?
Upgrade affected software to a fixed version, for example Redhat Openshift Ai 2.25.7 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-1462 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.