DE EN IT

~/exploited / cve-2026-40217

CVE-2026-40217: BerriAI LiteLLM

According to CISA this vulnerability is already used in attacks (added on 18 November 2026).

Key facts

CVECVE-2026-40217
VendorBerriAI — LiteLLM
VulnerabilityBerriAI LiteLLM Unprotected Alternate Channel Vulnerability
Added18 November 2026
Deadline (US agencies)2 December 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.8 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: low needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 17.02%. Higher than 97.1% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-420
CWE-94 — Code Injection
Affected versionslitellm: <= 2026-04-08

Description (NVD)

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

Description (CISA)

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.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether BerriAI LiteLLM is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 18 November 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).