A user who can reach the guardrail test function can break its Python restrictions and execute code in the proxy process. In the default configuration, the vendor says that function requires a proxy-admin credential. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 18 November 2026.The vendor's version table lists LiteLLM 1.81.8 through versions before 1.83.10 as affected. Its patch instructions instead say to upgrade to 1.83.11 or later. Treat 1.83.10 as needing explicit vendor confirmation before calling it fixed.
What it allows
How Does CVE-2026-40217 Escape LiteLLM's Guardrail Sandbox?
LiteLLM lets authorized administrators test custom Python guardrail code. The affected implementation used source-level filtering and a custom execution sandbox. X41 found that bytecode rewriting could reach capabilities the filter intended to restrict. The result is code execution with the privileges of the running proxy process.
The default Docker image runs that process as root, according to both the vendor and X41. The vendor says a proxy-admin credential is required to reach the function in default configurations. CISA's KEV listing confirms exploitation of this CVE, but does not identify the exploited deployment configuration or an actor. It therefore does not establish an unauthenticated path.
The KEV addition changes the response priority for organizations running LiteLLM themselves. Brandefense Blackhole counted four dark-chat posts mentioning this CVE from 21 August through 19 November 2026. That count measures discussion, not incidents; CISA is the source for confirmed exploitation. The vulnerability intelligence platform supports prioritization of verified exposure and remediation work.
Who is affected
Which LiteLLM Deployments Need a CVE-2026-40217 Review?
Start with self-hosted LiteLLM proxy instances that run custom-code guardrails or expose the management interface. The vendor's affected-version field starts at 1.81.8 and ends before 1.83.10. X41 confirmed the flaw in a then-current main-latest Docker image, without giving a comparable release-number range.
There is an unresolved version boundary in the vendor advisory: its table calls 1.83.10 patched, while its patch paragraph says the fix is in 1.83.11. Use 1.83.11 or a later vendor-confirmed fixed release as the upgrade target. Check the version running in each process or container after rollout, rather than relying on a package manifest alone.
Review who holds proxy-admin or master-key access, where the management interface is reachable, and whether the guardrail test function was invoked unexpectedly. Access and application logs can help scope review, but a request alone does not prove sandbox escape. Public repository mentions alone do not validate exploit code or an incident. The vulnerability management guide explains how to record the fix and verification.
Timeline
- 2026-02-13
X41 says it identified the sandbox escape and created a proof of concept.
- 2026-04-08
X41 published its advisory after the disclosure embargo expired.
- 2026-04-10
NVD records the initial publication of CVE-2026-40217.
- 2026-05-07
The LiteLLM GitHub security advisory was published with version and patch information.
- 2026-11-18
CISA added CVE-2026-40217 to its Known Exploited Vulnerabilities catalog.
What to do
-
Inventory self-hosted proxies
Identify running LiteLLM proxy versions, custom-code guardrail use, management-interface exposure and identities with proxy-admin or master-key access.
-
Upgrade to a clearly fixed release
Follow the vendor patch paragraph and deploy LiteLLM 1.83.11 or later. Do not rely on the advisory's conflicting 1.83.10 version table without explicit confirmation.
-
Verify the running version
After deployment, check the version reported by each running proxy process or container and confirm it is 1.83.11 or a later vendor-confirmed fixed release.
-
Restrict the function until upgraded
Follow the vendor workaround by blocking the custom-code guardrail test function at the reverse proxy or API gateway. Limit management access and protect admin credentials.
-
Review possible misuse
Examine admin credential use and guardrail test activity for unexpected access. Investigate suspicious activity through the organization's incident process; log entries alone do not prove compromise.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-40217 in Brandefense Atlas
The Atlas record of CVE-2026-40217: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-40217 allow unauthenticated code execution?
The vendor says the affected function requires a proxy-admin credential in default configurations. CISA confirms exploitation but does not specify an unauthenticated path.
Which LiteLLM version should teams deploy?
The vendor's patch paragraph recommends 1.83.11 or later. Its version table says 1.83.10 is patched, so verify that release independently before treating it as fixed.
Why does the KEV listing matter?
CISA added CVE-2026-40217 on 18 November 2026, confirming known exploitation. The listing does not identify an actor, victim or affected deployment configuration.
Sources
- LiteLLM custom-code guardrail sandbox escape advisoryBerriAI GitHub Security Advisory
- X41-2026-001 LiteLLM guardrail sandbox escapeX41 D-Sec
- Known Exploited Vulnerabilities CatalogCISA
- CVE-2026-40217 recordNVD