Skip to content
Fencer Vulns
critical 9.8

CVE-2025-49655 json

Keras framework vulnerable to deserialization of untrusted data

published 2025-10-17 12 mo ago modified 2026-10-27 12 d ago also EUVD-2025-34892 , GHSA-cvhh-q5g5-qprp , PYSEC-2026-368

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

Deserialization of untrusted data can occur in versions of the Keras framework running versions 3.11.0 up to but not including 3.11.3, enabling a maliciously uploaded Keras file containing a TorchModuleWrapper class to run arbitrary code on an end user’s system when loaded despite safe mode being enabled. The vulnerability can be triggered through both local and remote files.

Patch / fix

  • pypi keras 3.11.3
  • Keras Keras 3.11.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-49655 updated cvss 8.4

keras: Keras deserialization of untrusted data

  • Red Hat OpenShift AI 2.25 rhoai v2.25.1-1764825096, rhoai v2.25.1-1764961121, rhoai v2.25.1-1765326513, rhoai v2.25.1-1765613316
    fixed: vendor fix RHSA-2025:23531
  • Red Hat Trusted Artifact Signer 1.3 rhtas 0.0.2-1763378239
    fixed: vendor fix RHSA-2025:22068
  • Red Hat OpenShift AI (RHOAI) odh-modelmesh-runtime-adapter-rhel8, odh-pipeline-runtime-minimal-cpu-py311-rhel9, odh-pipeline-runtime-pytorch-cuda-py311-rhel9, odh-pipeline-runtime-pytorch-rocm-py311-rhel9, odh-workbench-jupyter-minimal-cpu-py311-rhel9, odh-workbench-jupyter-minimal-cuda-py311-rhel9, +11 more
    not affected: component not present
  • Red Hat OpenShift AI 2.25 rhoai 0.0-1763988459, rhoai v2.25.1-1764757768, rhoai v2.25.1-1764757769, rhoai v2.25.1-1764757770, rhoai v2.25.1-1764757772, rhoai v2.25.1-1764757773, +33 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
12 mo ago

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi keras
>=3.11.0, <3.11.3
3.11.3

Affected products

  • Keras Keras

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.