Source: LiteLLM blog: CVE-2026-42208, SQL injection in LiteLLM Proxy
LiteLLM's own post on a pre-authentication SQL injection in the proxy's API-key verification path, affecting v1.81.16-v1.83.6 and fixed in v1.83.7.
Contents
- What: vendor security post
- Publisher: BerriAI (LiteLLM); authors Krrish Dholakia and Ishaan Jaffer
- Date: 2026-04-29
- Original: docs.litellm.ai/blog/cve-2026-42208-litellm-proxy-sql-injection; advisory GHSA-r75f-5x8p-qvmc
Summary
The post discloses that a crafted Authorization: Bearer value on an unauthenticated request could, under some conditions, reach a vulnerable database query during API-key verification. It was reported through the bug bounty programme and fixed before the advisory went out.
Key claims
- Affected: v1.81.16 through v1.83.6. Fixed: v1.83.7 and later. Recommended: v1.83.10-stable.
- Impact depends on configuration, network exposure, database permissions and what is stored.
- Operators whose proxy was reachable from untrusted networks on an affected version should review Postgres query history (the post links a helper query).