Exploited vulnerabilities / CVE-2026-40217
Confirmed exploited · remote code execution · BerriAI LiteLLMCVE-2026-40217
BerriAI LiteLLM remote code execution, confirmed exploited in the wild.
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.
| CISA's name for it | BerriAI LiteLLM Unprotected Alternate Channel Vulnerability |
|---|---|
| Vendor and product | BerriAI · LiteLLM |
| Type | remote code execution · CWE-420 |
| Severity | High 8.8 CVSS base score |
| Affected versions | LiteLLM: bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f |
| First published | 10 April 2026 |
| Weakness | CWE-420 Unprotected Alternate Channel |
| Exploited | Confirmed by CISA listed 18 November 2026 |
| Likelihood | one of the most likely to be exploited of every vulnerability tracked |
| Deadline | 2 December 2026 · 13 days left |
| Used in ransomware | Not reported |
| Advisories | github.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗ |
Three steps, in this order
Patch to the fixed version the vendor names, today if the product faces the internet.
Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.
Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
| CISA's required action | 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. |
|---|
Know before someone else finds it
Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.
CVE-2026-40217 in short
Is CVE-2026-40217 being exploited?
Yes. CISA added CVE-2026-40217 to its Known Exploited Vulnerabilities catalogue on 18 November 2026, which it does only on evidence of exploitation in the wild.
What is the CISA deadline for CVE-2026-40217?
US federal agencies must remediate it by 2 December 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.
How likely is CVE-2026-40217 to be exploited in the next 30 days?
FIRST's Exploit Prediction Scoring System gives it 17%, the 97th percentile of every CVE it scores.
Which versions of BerriAI LiteLLM are affected by CVE-2026-40217?
According to the CVE record: LiteLLM: bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f. Check the vendor's advisory for the fixed version.
How do I fix CVE-2026-40217?
Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
Other BerriAI vulnerabilities being exploited
| CVE | Product | Type | Listed |
|---|---|---|---|
| CVE-2026-59822 | LiteLLM | authentication bypass | 2 September 2026 |
| CVE-2026-42271 | LiteLLM | command injection | 8 June 2026 |
| CVE-2026-42208 | LiteLLM | SQL injection | 8 May 2026 |
Sources: CISA Known Exploited Vulnerabilities catalogue (released 18 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 19 November 2026.