litellm
Affected
- introduced
1.81.16, fixed1.83.7(ecosystem)
Fixed versions
1.83.7
Fix
- Fixed version
1.83.7pip install --upgrade litellm==1.83.7
Advisory
Also known as: CVE-2026-42208, PYSEC-2026-391
LiteLLM has SQL Injection in Proxy API key verification
Impact
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.
Patches
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.
Workarounds
If upgrading is not immediately possible, set disable_error_logs: true under general_settings. This removes the path through which unauthenticated input reaches the vulnerable query.
References
Discovery Credit: Tencent YunDing Security Lab
Critical Basis: The source's own band: CRITICAL
1.81.16, fixed 1.83.7 (ecosystem)1.83.7
1.83.7pip install --upgrade litellm==1.83.7Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0