CVE-2026-40217

CVE-2026-40217 is a high-severity vulnerability in Litellm with a CVSS 3.x base score of 8.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-11-18). The underlying weakness is classified as CWE-420.

Key facts

Description

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

Frequently asked questions

What is CVE-2026-40217?
LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
How severe is CVE-2026-40217?
CVE-2026-40217 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-40217 being actively exploited?
Yes. CVE-2026-40217 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-11-18, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2026-40217?
CVE-2026-40217 primarily affects Litellm. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-40217?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2026-40217 have an EU (EUVD) identifier?
Yes. CVE-2026-40217 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-21376.
When was CVE-2026-40217 published?
CVE-2026-40217 was published on 2026-04-10 and last updated on 2026-11-19.

References

Affected products (4)

More vulnerabilities in Litellm

All CVEs affecting Litellm →

Other CWE-420 vulnerabilities

Browse all CWE-420 vulnerabilities →