CVE-2026-1462 | keras up to 3.13.1 TFSMLayer from_config deserialization

VDB-357169 · CVE-2026-1462 · GCVE-0-2026-1462 KERAS UP TO 3.13.1 TFSMLAYER FROM_CONFIG DESERIALIZATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.4 $0-$5k 1.13+ Summaryinfo A vulnerability, which was classified as critical, has been found in keras up to 3.13.1. Affected is the function from_config of the component TFSMLayer. This manipulation causes deserialization. The identification of this vulnerability is CVE-2026-1462. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component. Detailsinfo A vulnerability has been found in keras up to 3.13.1 and classified as critical. Affected by this vulnerability is the function from_config of the component TFSMLayer. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: 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. The advisory is shared at huntr.com. This vulnerability is known as CVE-2026-1462 since 01/27/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. Upgrading to version 3.13.2 eliminates this vulnerability. Productinfo Name keras Version 3.13.0 3.13.1 CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.6 VulDB Meta Temp Score: 7.4 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.8 CNA Vector (@huntr_ai): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Deserialization CWE: CWE-502 / CWE-20 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: keras 3.13.2 Timelineinfo 01/27/2026 CVE reserved 04/13/2026 +75 days Advisory disclosed 04/13/2026 +0 days VulDB entry created 04/13/2026 +0 days VulDB entry last update Sourcesinfo Advisory: huntr.com Status: Confirmed CVE: CVE-2026-1462 (🔒) GCVE (CVE): GCVE-0-2026-1462 GCVE (VulDB): GCVE-100-357169 Entryinfo Created: 04/13/2026 17:28 Changes: 04/13/2026 17:28 (63) Complete: 🔍 Cache ID: 99:BFA:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸