CVE-2026-40217

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 6.5%, top 7% 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, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 15%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
15%
EPSS %ILE
96%
KEV
Not listed

Published

April 10, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Advisory X41-2026-001: Guardrail Sandbox Escape in LiteLLM | X41 D-Sec - Penetration Tests and Source Code Audits

https://www.x41-dsec.de/lab/advisories/x41-2026-001-litellm/

Vendor Advisories for CVE-2026-40217(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 / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17823100082026-06-25redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17801027322026-06-09redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
litellm1.81.10 ... 1.83.9 (27 versions)1.83.10—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-40217.yaml
    First seen Jan 1, 2026

    LiteLLM < 1.25.0 - Remote Code Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-40217?
CVE-2026-40217 is a high vulnerability published on April 10, 2026. LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/testcustomcode URI.
When was CVE-2026-40217 disclosed?
CVE-2026-40217 was first published in the National Vulnerability Database on April 10, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40217 actively exploited?
CVE-2026-40217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15% probability of exploitation in the next 30 days, which ranks it in the top 3.5% of all scored CVEs.
What is the CVSS score of CVE-2026-40217?
CVE-2026-40217 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-40217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40217, 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-40217

Explore →

Is Your Infrastructure Affected by CVE-2026-40217?

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

Start Free Scan →Browse All CVEs