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.5%, top 62% 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: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 8, 2026

Advisory Details (1)

Auto-updated Jul 26, 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(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 65× 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.

  1. 2026-07-27 00:52 UTCGHSA enrichment
  2. 2026-07-26 20:30 UTCGHSA enrichment
  3. 2026-07-26 16:44 UTCEG score recompute
  4. 2026-07-26 16:44 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 12:55 UTCEG score recompute
  8. 2026-07-26 12:55 UTCGHSA enrichment
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:05 UTCEG score recompute▲ 1.00
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-21 15:24 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 02:28 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-17 04:17 UTCGHSA enrichment
  20. 2026-07-16 17:21 UTCGHSA enrichment
  21. 2026-07-16 17:02 UTCEPSS rescore
  22. 2026-07-16 06:05 UTCGHSA enrichment
  23. 2026-07-15 19:08 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 08:12 UTCGHSA enrichment
Show 40 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 21:16 UTCGHSA enrichment
  3. 2026-07-14 10:20 UTCGHSA enrichment
  4. 2026-07-13 23:23 UTCGHSA enrichment
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 12:27 UTCGHSA enrichment
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-13 01:30 UTCGHSA enrichment
  9. 2026-07-12 14:33 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 03:37 UTCGHSA enrichment
  12. 2026-07-11 16:41 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 05:45 UTCGHSA enrichment
  15. 2026-07-10 18:49 UTCGHSA enrichment
  16. 2026-07-10 07:53 UTCGHSA enrichment
  17. 2026-07-09 20:52 UTCGHSA enrichment
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 09:55 UTCGHSA enrichment
  20. 2026-07-08 22:59 UTCGHSA enrichment
  21. 2026-07-08 15:15 UTCEPSS rescore
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 15:13 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  24. 2026-07-08 11:59 UTCGHSA enrichment
  25. 2026-07-08 01:02 UTCGHSA enrichment
  26. 2026-07-07 14:05 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 03:08 UTCGHSA enrichment
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 16:11 UTCGHSA enrichment
  31. 2026-07-06 05:15 UTCGHSA enrichment
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-05 18:18 UTCGHSA enrichment
  34. 2026-07-05 07:19 UTCGHSA enrichment
  35. 2026-07-05 02:30 UTCEPSS rescore
  36. 2026-07-05 02:30 UTCEPSS rescore
  37. 2026-07-04 20:22 UTCGHSA enrichment
  38. 2026-07-04 09:26 UTCGHSA enrichment
  39. 2026-07-03 22:30 UTCEG score recompute
  40. 2026-07-03 22:30 UTCGHSA enrichment

Related CVEs(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 0% probability of exploitation in the next 30 days, which ranks it in the top 62.1% 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

Explore the affected products and dependency analysis for 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