← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-40217 exploited? Yes: in CISA KEV since 18 Nov 2026

Gociux · BerriAI LiteLLM · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-40217, BerriAI LiteLLM Unprotected Alternate Channel Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 18 Nov 2026, 222 days after it was published. It affects BerriAI LiteLLM. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 18 Nov 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity8.8CVSS 3.1 · high
US federal due2 Dec 2026BOD 22-01 deadline

What it is

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.

VendorBerriAI (4 exploited CVEs in KEV)
ProductLiteLLM
VulnerabilityBerriAI LiteLLM Unprotected Alternate Channel Vulnerability
WeaknessCWE-420
Published10 Apr 2026
Added to KEV18 Nov 2026
Reported by (CNA)mitre

What to do

  1. Check whether you run it. Look for LiteLLM in your asset inventory, including appliances and cloud images. Stack check lists every exploited BerriAI CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 10 Apr 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for BerriAI.

Other exploited CVEs in LiteLLM

References

Questions

Is CVE-2026-40217 being exploited?

Yes. CISA added CVE-2026-40217 to the Known Exploited Vulnerabilities catalog on 18 Nov 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-40217 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-40217?

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 BerriAI's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected LiteLLM and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in November 2026 · BerriAI scorecard · act-now radar.

Running BerriAI in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →