Browse / AI Framework and Platform Flaws / CVE-2026-42208
LiteLLM has SQL Injection in Proxy API key verification
- Class
- AI Framework and Platform Flaws (grouped automatically from the text)
- Technique
- SQL and query injection
- Affected
- litellm (PyPI)
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 89.4% chance of exploitation in 30 days
Details
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
- Patched release:
v1.83.7-stable
Discovery Credit: Tencent YunDing Security Lab
References
- https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc
- https://nvd.nist.gov/vuln/detail/CVE-2026-42208
- https://access.redhat.com/security/cve/CVE-2026-42208
- https://bugzilla.redhat.com/show_bug.cgi?id=2463965
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable
- https://github.com/advisories/GHSA-r75f-5x8p-qvmc
- https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-391.yaml
- https://pypi.org/project/litellm
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42208
Source: GitHub Advisory Database, used under CC BY 4.0.