CVE-2026-40217: BerriAI LiteLLM flaw exploited in the wild, what we know
CVE-2026-40217 affects BerriAI LiteLLM; exploited in the wild. What happened, who is affected, how far exploitation has gone and where the patch stands.
CVE-2026-40217 at a glance
CVE-2026-40217 is a high-severity Code Injection vulnerability in BerriAI LiteLLM, with a CVSS 3.1 base score of 8.8. NVD published it on 2026-04-10 and classifies the weakness as CWE-420 and CWE-94. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-18; the federal remediation due date is 2026-12-02. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 17.02% (percentile 97.1, scored 2026-11-18). NVD lists affected versions up to and including 2026-04-08 for litellm litellm but no fixed release; the vendor advisory has the fix. CVERadar maps 3 MITRE ATT&CK techniques across Initial Access and Execution, inferred from the CWE and the description. Its CVERadar threat level is 64/100.
Full CVE-2026-40217 record: exploitation evidence, ATT&CK chain and every source.
What it is
Who's affected
Anyone running BerriAI LiteLLM in the version ranges below. Internet-facing instances are the priority.
- litellm litellm: up to and including 2026-04-08.
Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.
Exploitation status
- Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-18; federal remediation due date 2026-12-02.
What this means for a small business
CISA added CVE-2026-40217 to its Known Exploited Vulnerabilities catalog on 2026-11-18. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.
If your business runs BerriAI LiteLLM, put this at the top of the patch list. CISA gave US federal agencies until 2026-12-02 to deal with it, and that is a sensible deadline for a small business too.
- Patch. Install the latest update from BerriAI. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
- If you cannot patch yet. Follow 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.
- Check your exposure. Find out whether BerriAI LiteLLM can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
- When to call IT support. Call your IT support provider now if you run BerriAI LiteLLM and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.
Risk
- EPSS (probability of exploitation activity in the next 30 days): 17.02%, higher than 97% of all scored CVEs (as of 2026-11-18).
- CVERadar threat level: 64/100 (see methodology).
- Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1059 Command and Scripting Interpreter (inferred); T1203 Exploitation for Client Execution (inferred).
Remediation steps
- Find every instance. List where BerriAI LiteLLM runs, including test, DR and forgotten internet-facing systems, and record the installed version.
- Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.
- If you can't patch today, follow 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.
- Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
- Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
- Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.
Detection hints
- T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to LiteLLM (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-04-10.
- T1059 Command and Scripting Interpreter: Watch for the service process spawning shells or script interpreters.
- T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.
Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.
Sources
- NVD: CVE-2026-40217 nvd.nist.gov/vuln/detail/CVE-2026-40217
- CVE.org record www.cve.org/CVERecord?id=CVE-2026-40217
- Vendor link from CISA KEV github.com/BerriAI/litellm/security/advisories/GHSA-wxxx-gvqv-xp7p
- Mitigation www.x41-dsec.de/lab/advisories/x41-2026-001-litellm/
- CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
- FIRST EPSS (2026-11-18) api.first.org/data/v1/epss?cve=CVE-2026-40217
Track every exploited CVE
Full record for CVE-2026-40217, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.