Exploited CVEs / CVE-2026-42208

CVE-2026-42208

BerriAI LiteLLM SQL Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-05-11 (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.

Senserva AI read on CVE-2026-42208CISA required actionOfficial fix for CVE-2026-42208Admin questions

Risk summary

CriticalCISA KEV
9.8
CVSS v3 base
89%
EPSS exploit probability
Critical
Severity
2026-05-08
Added to KEV
2026-05-11 (past due)
CISA due date

Actively exploited BerriAI LiteLLM vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2026-05-08.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-05-11; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated May 8, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2026-42208

LiteLLM is an LLM proxy that stores the API keys and credentials for every model provider it fronts, so a SQL injection here exposes far more than a typical database read. CVE-2026-42208 (Severity: Critical, CVSS 9.8) lets an attacker read and potentially modify the proxy's database, which can mean unauthorized access to the proxy and every credential it manages. CISA added it to KEV on 2026-05-08 and EPSS puts exploit probability at 89%, so anyone running an internet-reachable LiteLLM proxy should treat it as under active attack.

Do this: Upgrade BerriAI LiteLLM to the vendor's patched release today, restrict network access to the proxy, and rotate every provider API key and credential stored in it, since they may already be exposed.

AI-generated from public data, 2026-11-18. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-42208

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2026-42208

Published
2026-05-08
Last revised
2026-05-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.

Senserva Watchevery change we have recorded for this one
What changed, and when

CVE-2026-42208's EPSS exploitation probability fell from 89.4% to 5.8% on 2026-09-24, then returned to 89.4% on 2026-10-25. The current 89.4% is the strongest signal: the dip was temporary and exploitation likelihood is back at its earlier peak. Treat this as high priority today and patch rather than relying on the earlier drop.

0%25%50%75%100%CISA KEVCISA KEV on 2026-05-082026-07-17: EPSS 87%2026-07-24: EPSS 87%2026-07-30: EPSS 89%2026-09-24: EPSS 5.8%2026-10-25: EPSS 89%EPSS 89%2026-05-082026-10-25

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-05-08 added to the CISA KEV catalog by CISA
  • 2026-07-17 EPSS first scored at 86.6%
  • 2026-07-24 EPSS 86.6% to 87.3%
  • 2026-07-30 EPSS 87.3% to 89.4%
  • 2026-09-24 EPSS 89.4% to 5.8%
  • 2026-10-25 EPSS 5.8% to 89.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-05-11 (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-42208

Check the vendor's security advisory channel for the patched LiteLLM versions and workarounds.

Common questions about CVE-2026-42208

Is CVE-2026-42208 actively exploited?

Yes. CVE-2026-42208 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-05-08, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 89%.

What is the CISA deadline and required action for CVE-2026-42208?

CISA set the federal remediation due date at 2026-05-11, 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-42208?

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-42208?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-42208'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.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.