CVE-2026-42208criticalunder attackCWE-89

CVE-2026-42208: critical vulnerability in BerriAI litellm

LiteLLM: SQL injection in Proxy API key verification

Published · Updated

Follow this CVE+ Monitor litellm+ Monitor litellm

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

100Vexday Risk Score

Patch now. It under exploitation confirmed by CISA and has a working public exploit.

ssvc Actcvss 9.3epss 89%
from disclosure to weaponsame day
Published on NVDMay 8
1st PoCApr 28
metasploitApr 20
CISA KEVMay 8
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Not affected
3 products (4 components) — because the vulnerable code is not present in the product
Red Hat OpenShift AI (RHOAI) · Lightspeed Core · Red Hat Ansible Automation Platform 2
Action required by CISAfederal deadline: 2026-05-11

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

In short

LiteLLM proxy server has a SQL injection flaw in its API key verification. An attacker can send a specially crafted Authorization header to bypass authentication and read or modify the database, potentially stealing credentials and gaining unauthorized access.

Technical detail

SQL injection vulnerability in database query during API key verification (CWE-89) due to unsanitized concatenation of user-supplied Authorization header values into query text. Unauthenticated attackers can exploit this via POST requests to LLM API routes to extract or modify database records, including stored credentials. Affects versions 1.81.16 through 1.83.6.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.81.16 to before version 1.83.7, a database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted Authorization header to any LLM API route (for example POST /chat/completions) and reach this query through the proxy's error-handling path. An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages. This issue has been patched in version 1.83.7.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
BerriAI · litellm
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — BerriAI litellm

In the same product, most dangerous first.

CVE-2026-42271HIGHLiteLLM: Authenticated command execution via MCP stdio test endpointsEPSS 91.4%KEVCVE-2026-59822HIGHLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbackEPSS 0.8%KEVCVE-2026-35029HIGHLiteLLM affected by privilege escalation via unrestricted proxy configuration endpointEPSS 38.6%CVE-2026-49468CRITICALLiteLLM: Authentication Bypass via Host Header InjectionEPSS 3.0%CVE-2026-47101HIGHLiteLLM < 1.83.14 Privilege Escalation via API Key GenerationEPSS 1.2%CVE-2026-12773MEDIUMBerriAI litellm MCP Proxy user_api_key_auth_mcp.py UserAPIKeyAuth improper authenticationEPSS 1.0%