UTC
CriticalExploited in the wild (CISA KEV)

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
What it is

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.

What to do

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 you cannot upgrade yet

If upgrading is not immediately possible, set disableerrorlogs: true under general_settings. This removes the path through which unauthenticated input reaches the vulnerable query.

Affected
PackageRegistryAffectedFixed in
litellmPyPI>= 1.81.16, < 1.83.71.83.7

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].