Skip to main content
Black Friday: 40% off your first 3 months on any monthly plan with code BF40. Ends Dec 2.See the offer
Varaxon Technologies

Known exploited vulnerability · CISA KEV

CVE-2026-40217: BerriAI LiteLLM Unprotected Alternate Channel Vulnerability

BerriAI LiteLLM contains an unprotected alternate channel vulnerability that could allow remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.

CVE-2026-40217

Exploited in the wild. Fix this first.

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-18: attackers are using it right now.

CISA KEV
Listed
Added 2026-11-18 · federal fix-by 2026-12-02
EPSS (30 days)
62%
Higher than 99.2% of CVEs · 2026-11-19Up 59% in 30 days
CVSS v3.1
8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What CISA says

BerriAI LiteLLM Unprotected Alternate Channel Vulnerability

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

NVD description · published 2026-04-10

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

Full record on NVD

Got a whole scan? Scan Hub runs this check on every finding in your Nessus, Qualys, Rapid7 or OpenVAS export and ranks the report by it.

Try it free

CVE-2026-40217 in plain words

Written by Varaxon from the sources below. Last checked .

What an attacker can do
The LiteLLM proxy has a /guardrails/test_custom_code endpoint that runs Python code sent to it inside a home-made sandbox. The sandbox can be escaped with bytecode tricks, which lets the caller run any code in the proxy process. That process runs as root in the default Docker image. LiteLLM says reaching the endpoint needs a proxy admin credential in default setups, and the finder, X41 D-Sec, says it needs the master key.
Who is affected
LiteLLM 1.81.8 up to but not including 1.83.10, per the LiteLLM advisory on GitHub. NVD describes it as LiteLLM through 2026-04-08.
What to do first
The LiteLLM advisory lists 1.83.10 as the first patched version and its text says to upgrade to 1.83.11 or later, where the sandbox was replaced with RestrictedPython; 1.83.11 or later covers both. If you cannot upgrade yet, block POST /guardrails/test_custom_code at your reverse proxy or API gateway, keep the master key with trusted admins only, and keep the admin port off untrusted networks.

How to check if you are exposed to CVE-2026-40217

  1. Find every BerriAI LiteLLM system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
  2. Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
  3. Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2026-40217.

US federal agencies had to fix this by 2026-12-02. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.

Affected versions

Versions the National Vulnerability Database lists as vulnerable to CVE-2026-40217. Check the vendor advisory for the exact fixed builds before you sign anything off.

ProductVulnerable versions
Litellmfrom 1.81.8 before 1.83.10
Redhat Ansible Automation Platformfrom 2.0 before 2.6-9
Redhat Openshift AIfrom 3.3 before 3.3.4
Redhat Openshift Lightspeedall versions

Timeline

  1. · Published in the National Vulnerability Database
  2. · Added to CISA's Known Exploited Vulnerabilities catalog, 222 days after it was published
  3. · Fix-by date for US federal agencies, still ahead

Vendor advisories and fixes

Weakness type

More exploited BerriAI vulnerabilities

CISA lists 4 exploited BerriAI vulnerabilities. The closest matches:

Keep going

Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.11.18); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-20. This product uses the NVD API but is not endorsed or certified by the NVD.

Cookie preferences

Essential site functions remain available whichever option you choose. Your advertising choice is saved on this site. The Scan Hub has a separate choice.

Google and Reddit may receive cookies, identifiers, browser and device information, and your network/IP information. Reject or withdraw at any time. Read the Privacy Policy.