Skip to main content
VulnerabilityPublished Updated

CVE-2026-12481: keras-team/keras · Deserialization of Untrusted Data

Affects keras-team/kerasSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High · patch available : patch keras-team/keras soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
keras-teamkeras-team/kerasAffected
  • ≥ unspecified, ≤ latest
Fixed in–

AI-suggested

Since this is a cloud-hosted service, the vendor manages remediation server-side. Users should consult the vendor advisory for confirmation of patch deployment and ensure they are using a version with the fix applied. Avoid invoking Lambda.from_config(config) or related deserialization functions outside of a SafeModeScope(True) context until patched. Patch status is confirmed as available, but specific patch versions are not listed; check the vendor advisory for current remediation guidance.

Description

CVE-2026-12481 is a high-severity vulnerability in keras-team/keras version 3.14.0 involving unsafe deserialization in the Lambda layer. The issue arises because the _raise_for_lambda_deserialization() function does not properly enforce safe-mode when safe_mode is None, which is the default outside a SafeModeScope context. This allows attacker-controlled marshal bytecode to be deserialized, potentially leading to arbitrary OS-level code execution. The vulnerability affects calls to keras.layers.deserialize(config), keras.models.clone_model(model), and Lambda.from_config(config) without SafeModeScope(True). The product is a cloud service, and a patch is available. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…