CVE-2026-42208: LiteLLM has SQL Injection in Proxy API key verification
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.
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.
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.
How to check
- Affected: litellm (pip) >= 1.81.16, < 1.83.7.
- Compare your installed version with the range above (command below).
How to fix
- Upgrade litellm to 1.83.7 or later.
pip show litellm | grep Version