LiteLLM has SQL Injection in Proxy API key verification
CVE-2026-42208 · GHSA-r75f-5x8p-qvmc · published 2026-04-24 · updated 2026-10-05
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 89.4%
- Fixed in
- 1.83.7
Known exploited
CISA added this to its Known Exploited Vulnerabilities catalog on 2026-05-08; US federal agencies had until 2026-05-11 to act. CISA's 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.
- Exploitation Exploited in the wild
- Automatable Yes
- Technical impact Total
- CISA SSVC
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.
Upgrade litellm to 1.83.7 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Fixed in 1.83.7. The caller-supplied value is now always passed to the database as a separate parameter. Upgrade to 1.83.7 or later.
If upgrading is not immediately possible, set disableerrorlogs: true under general_settings. This removes the path through which unauthenticated input reaches the vulnerable query.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| litellm | PyPI | >= 1.81.16, < 1.83.7 | 1.83.7 |
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalLangflow: Weak Fernet Key via random.seed()langflow
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalLiteLLM vulnerable to server-side template injection in the /prompts/test endpointlitellm
- CriticalMalicious code in litellm (PyPI)litellm, litellm, litellm
- CriticalLiteLLM: Authentication Bypass via Host Header Injectionlitellm
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.