CVE-2026-42208
LiteLLM: SQL injection in Proxy API key verification
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.
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 · litellmpublic PoCs found — 5
githubgithub.com/Zeltoc/threat-intel-brief-cve-2026-42208-litellm★ 0githubgithub.com/ridhinva/litellm-sqli-scanner★ 0githubgithub.com/HAERIN-L/poc_cve-2026-42208★ 0githubgithub.com/yendpoint/CVE-2026-42208-LAB★ 0githubgithub.com/rootdirective-sec/CVE-2026-42208-Lab★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Want to know if your infrastructure is exposed to this?
Talk to TrueHacking →