keras-team/keras: Deserialization of Untrusted Data
CVE-2026-1462 is a high-severity deserialization of untrusted data vulnerability in keras-team/keras from Keras-team, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 3.13.2 as the first without the flaw, so updating keras-team/keras to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.42% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update keras-team/keras to 3.13.2 or a later version.
- Update Openshift Ai to 2.25.7 or a later version.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Keras-team | keras-team/keras | before 3.13.2 | 3.13.2 |
| Red Hat | Red Hat OpenShift AI 2.25 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI 3.3 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
| Keras | Keras | 3.13.0 | Not stated |
| Red Hat | Openshift Ai | 2.25 up to, but not including, 2.25.7 | 2.25.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.0 | 8.8 | High | CNA (huntr.dev) |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- access.redhat.com/errata/RHSA-2026:24977Third Party Advisory
- access.redhat.com/security/cve/CVE-2026-1462Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2457856Issue Tracking, Third Party Advisory
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1462.jsonThird Party Advisory
Technical write-ups (may include proof of concept)
- huntr.com/bounties/7e78d6f1-6977-4300-b595-e81bdbda331cExploit, Third Party Advisory
Other references
Other vulnerabilities in keras-team/keras
- 7.8 High severity
- 9.8 Critical severity
- 8.1 High severity
- 8.0 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.