CVE-2026-12481

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A vulnerability in keras-team/keras version 3.14.0 allows for arbitrary code execution due to improper handling of deserialization in the Lambda layer. Specifically, the _raise_for_lambda_deserialization() function fails to enforce the safe-mode guard when safe_mode is set to None, which is the default value when from_config() is called outside of a SafeModeScope context. This logic error conflates None (unset/default-deny) with False (explicitly disabled), bypassing the guard and allowing attacker-controlled marshal bytecode to be deserialized. Affected call sites include keras.layers.deserialize(config), keras.models.clone_model(model), and any direct invocation of Lambda.from_config(config) without an enclosing SafeModeScope(True). This vulnerability can be exploited to achieve arbitrary OS-level code execution in the context of the server or user process.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
60(Track*)
EG Risk 60/100SSVC: Track*

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%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 8, 2026

Advisory Details (1)

Auto-updated Sep 13, 2026
No patch confirmed yet.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/59ceaed1-c8a3-4135-8f94-169ade02823d

Vendor Advisories for CVE-2026-12481(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-kserve-storage-initializer-rhel9:17870734792026-08-27redhat

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 rangeFixed inDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1——
PyPI(1)
PackageVulnerable rangeFixed inDependents
keras0.2.0 ... 3.9.2 (120 versions)3.15.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 53× 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 235 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-12481?
CVE-2026-12481 is a critical vulnerability published on July 3, 2026. A vulnerability in keras-team/keras version 3.14.0 allows for arbitrary code execution due to improper handling of deserialization in the Lambda layer. Specifically, the raiseforlambdadeserialization() function fails to enforce the safe-mode guard when safemode is set to None, which is the default…
When was CVE-2026-12481 disclosed?
CVE-2026-12481 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12481 actively exploited?
CVE-2026-12481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.6% of all scored CVEs.
What is the CVSS score of CVE-2026-12481?
CVE-2026-12481 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-12481?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12481, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12481

Explore →

Is Your Infrastructure Affected by CVE-2026-12481?

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

Start Free Scan →Browse All CVEs