Exploited CVEs / CVE-2026-42271
CVE-2026-42271
BerriAI LiteLLM Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-06-22 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Risk summary
Actively exploited BerriAI LiteLLM vulnerability, High severity, CVSS v3 8.8. Added to the CISA KEV catalog 2026-06-08.
Updated June 8, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-42271
This LiteLLM flaw lets any authenticated user, even those with low-privilege internal-user keys, execute arbitrary commands on the host, so the usual assumption that authentication limits blast radius does not hold here. CISA confirmed active exploitation and added it to the KEV catalog on 2026-06-08, and with an 83 percent EPSS score the exploitation risk is immediate. Anyone running LiteLLM as an AI gateway with issued API keys is exposed.
Do this: Identify all LiteLLM deployments and patch to a fixed version now, and in the interim revoke or rotate low-privilege internal-user keys and restrict network access to the LiteLLM host.
AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-42271
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-42271
- Published
- 2026-06-08
- Last revised
- 2026-06-08
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
The strongest signal is the current EPSS of 91.4%, still near its 92.6% peak from 2026-09-29. After a brief collapse to 12.8% on 2026-09-24, the score rebounded within five days and has held steady since. That swing suggests the early drop was noise, so treat this CVE as high exploitation likelihood and prioritize remediation today.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-06-08 added to the CISA KEV catalog by CISA
- 2026-07-17 EPSS first scored at 80.2%
- 2026-07-24 EPSS 80.2% to 83.0%
- 2026-08-24 EPSS 83.0% to 83.5%
- 2026-08-29 EPSS 83.5% to 83.6%
- 2026-09-24 EPSS 83.6% to 12.8%
- 2026-09-29 EPSS 12.8% to 92.6%
- 2026-10-25 EPSS 92.6% to 91.4%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
CISA required action
Federal remediation due date: 2026-06-22 (past due).
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Official fix for CVE-2026-42271
Check the vendor's security advisory channel for the patched LiteLLM versions and workarounds.
Common questions about CVE-2026-42271
Is CVE-2026-42271 actively exploited?
Yes. CVE-2026-42271 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-06-08, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 91%.
What is the CISA deadline and required action for CVE-2026-42271?
CISA set the federal remediation due date at 2026-06-22, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
What fixes CVE-2026-42271?
Check the vendor's security advisory for the patched LiteLLM versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-42271?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-42271's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).
Scope and sources
- More exploited BerriAI CVEs
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.