CVE-2025-49655

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

Published

October 17, 2025

Last Modified

April 15, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

Disable `torch.load` in `TorchModuleWrapper` when in safe mode.

Patch available: keras-team/keras v3.12.0 (PR #21575 merged 2025-08-12)

https://github.com/keras-team/keras/pull/21575

Vendor Advisories for CVE-2025-49655(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:sha256:2d0c6bb9a4e81ea6a20b9ca4fde13108b56b3f91fa8e902c528c322288a380332025-12-17redhat
redhatrhtas/model-transparency-rhel9:sha256:cdbf79af3951e2830df94331a890ab8f1e2649db72e96bec57fee61fc9add1e62025-11-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
keras3.11.0, 3.11.1, 3.11.2
  • 3.11.0 up to 3.11.3: fixed in 3.11.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 214 total refreshes for this CVE.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:10 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-06 08:19 UTCOSV refresh
  7. 2026-10-05 17:42 UTCEPSS rescore
  8. 2026-10-04 23:21 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-28 13:50 UTCEPSS rescore
  14. 2026-09-27 13:45 UTCEPSS rescore
  15. 2026-09-26 15:58 UTCEPSS rescore
  16. 2026-09-26 00:25 UTCEPSS rescore
  17. 2026-09-24 14:02 UTCEPSS rescore
  18. 2026-09-24 14:02 UTCEPSS rescore
  19. 2026-09-23 13:47 UTCEPSS rescore
  20. 2026-09-21 21:06 UTCEPSS rescore
  21. 2026-09-20 20:15 UTCEPSS rescore
  22. 2026-09-20 20:15 UTCEPSS rescore
  23. 2026-09-18 19:27 UTCEPSS rescore
  24. 2026-09-18 19:27 UTCEPSS rescore
  25. 2026-09-17 19:29 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 15:39 UTCOSV refresh
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-15 03:09 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 21:59 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-07 16:00 UTCEPSS rescore
  11. 2026-09-06 13:46 UTCEPSS rescore
  12. 2026-09-05 15:28 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:38 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-28 15:23 UTCOSV refresh
  21. 2026-08-27 14:24 UTCEPSS rescore
  22. 2026-08-26 14:45 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-24 14:16 UTCEPSS rescore
  25. 2026-08-24 09:22 UTCEPSS rescore
  26. 2026-08-23 00:18 UTCEPSS rescore
  27. 2026-08-21 23:48 UTCEPSS rescore
  28. 2026-08-20 22:54 UTCEPSS rescore
  29. 2026-08-19 17:03 UTCEPSS rescore
  30. 2026-08-18 13:47 UTCEPSS rescore
  31. 2026-08-17 13:46 UTCEPSS rescore
  32. 2026-08-16 14:55 UTCEPSS rescore
  33. 2026-08-16 02:13 UTCEPSS rescore
  34. 2026-08-15 01:29 UTCEPSS rescore
  35. 2026-08-13 21:59 UTCEPSS rescore
  36. 2026-08-12 13:50 UTCEPSS rescore
  37. 2026-08-12 04:04 UTCOSV refresh
  38. 2026-08-11 13:41 UTCEPSS rescore
  39. 2026-08-10 23:59 UTCEPSS rescore
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-08 16:36 UTCEPSS rescore
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-05 19:16 UTCEPSS rescore
  44. 2026-08-04 15:09 UTCEPSS rescore
  45. 2026-08-04 10:37 UTCEPSS rescore
  46. 2026-08-03 10:35 UTCEPSS rescore
  47. 2026-08-02 02:26 UTCEPSS rescore
  48. 2026-08-01 04:15 UTCEPSS rescore
  49. 2026-07-30 16:27 UTCEPSS rescore
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-28 15:35 UTCEPSS rescore
  53. 2026-07-27 09:39 UTCOSV refresh
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-25 14:17 UTCEPSS rescore
  56. 2026-07-25 14:17 UTCEPSS rescore
  57. 2026-07-24 14:17 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 02:57 UTCEG score recompute
  60. 2026-07-22 14:07 UTCEPSS rescore
  61. 2026-07-22 14:07 UTCEPSS rescore
  62. 2026-07-21 15:24 UTCEPSS rescore
  63. 2026-07-20 17:07 UTCEPSS rescore
  64. 2026-07-19 14:30 UTCEPSS rescore
  65. 2026-07-19 14:30 UTCEPSS rescore
  66. 2026-07-19 02:28 UTCEPSS rescore
  67. 2026-07-19 02:28 UTCEPSS rescore
  68. 2026-07-18 10:04 UTCEPSS rescore
  69. 2026-07-16 17:02 UTCEPSS rescore
  70. 2026-07-16 17:02 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 01:59 UTCEPSS rescore
  74. 2026-07-15 01:59 UTCEPSS rescore
  75. 2026-07-13 22:29 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-49655?
CVE-2025-49655 is a critical vulnerability published on October 17, 2025. 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…
When was CVE-2025-49655 disclosed?
CVE-2025-49655 was first published on October 17, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-49655 actively exploited?
CVE-2025-49655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-49655?
CVE-2025-49655 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-49655?
A fix for CVE-2025-49655 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-49655 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49655

Explore →

Is Your Infrastructure Affected by CVE-2025-49655?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs