CVE-2026-40217: BerriAI LiteLLM Unprotected Alternate Channel
BerriAI LiteLLM · listed in the CISA catalog of actively exploited vulnerabilities since 2026-11-18.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 78%
- higher than 99.5% of all CVEs
- Added to CISA KEV
- 2026-11-18
- US federal due date 2026-12-02
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-40217 explained
CVE-2026-40217 is a code execution vulnerability in BerriAI LiteLLM, classified as an unprotected alternate channel (CWE-420). LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI. CISA lists it as known exploited, so affected servers should be addressed promptly.
Impact
An attacker with network access and low-privileged credentials can execute arbitrary code on the LiteLLM server without user interaction. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to exploit it. Ransomware use is unknown.
Who is affected
BerriAI LiteLLM is affected. The description states LiteLLM through 2026-04-08. The CVE record describes the affected version in free text, listing the identifier bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f. The CVE record names no fixed version. Check the vendor advisory for the current fix status.
Written with AI from the data on this page and checked against it automatically.
Official description
LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- BerriAI LiteLLMAffectedFixed in
- bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| BerriAI LiteLLMVersion statement as published by the CNA (free text). |
| not stated |
Also affected (reported by product suppliers)
- Red Hat Lightspeed CoreAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Lightspeed CoreAffected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: github.com/BerriAI/litellm/security/advisories/GHSA-wxxx-…
- CISA's deadline for US federal agencies: 2026-12-02 – a useful benchmark for everyone else, too.
What to do
- Follow the BerriAI vendor advisory and apply its mitigations or any fixed release it names.
- Restrict or block access to the /guardrails/test_custom_code endpoint until a fix is confirmed.
- Keep LiteLLM servers off the internet and limit access to trusted networks and users.
- Review and reduce low-privileged accounts and API keys that can reach the server.
- Check LiteLLM servers for signs of compromise, following CISA's forensics triage guidance.
- Discontinue use of the product if mitigations are unavailable, as CISA requires.
The CVE record names no fixed version. Follow the BerriAI vendor advisory for mitigations or updates. CISA requires applying vendor mitigations per BOD 26-04, following its guidance for cloud services, or discontinuing use if mitigations are unavailable. Meanwhile, restrict access to the /guardrails/test_custom_code endpoint, limit network exposure and check for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-420 Unprotected Alternate Channel
Questions about CVE-2026-40217
- Is CVE-2026-40217 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-11-18, with a US federal due date of 2026-12-02. Whether it is used in ransomware campaigns is unknown.
- Does an attacker need credentials?
- Yes, low privileges are required. No user interaction is needed, and the attack works over the network. Successful exploitation allows arbitrary code execution on the server.
- Which version fixes the issue?
- The CVE record names no fixed version. It states LiteLLM through 2026-04-08 is affected. Check the BerriAI vendor advisory for mitigations and fix status.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.