Skip to content
AI Sec Watch
CriticalVulnerabilityLLM-specific

GHSA-r75f-5x8p-qvmc: LiteLLM has SQL Injection in Proxy API key verification

Source
GitHub Advisory(opens in a new tab)
Identifier
GHSA-r75f-5x8p-qvmc
Published
Record updated
View JSON
Affected
  • litellm >= 1.81.16, < 1.83.7
Fixed in
1.83.7
  • released April 13, 2026, 11 days before disclosure

Summary

LiteLLM's proxy API key verification mixed the caller-supplied key value into a database query instead of passing it as a separate parameter, enabling SQL injection. An unauthenticated attacker can send a crafted Authorization header to any LLM API route, such as POST /chat/completions, and reach the query through the proxy's error-handling path. The attacker can read proxy database data and may modify it, gaining unauthorised access to the proxy and the credentials it manages.

Mitigation

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. If upgrading is not immediately possible, set disable_error_logs: true under general_settings, which removes the path through which unauthenticated input reaches the vulnerable query.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

  • litellmPyPILLM dependency since 2023-07-27 · 55 tracked dependents

Related items