LiteLLM: SQL injection in Proxy API key verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| BerriAI | litellm | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Berriai | Litellm |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r75f-5x8p-qvmc | LiteLLM has SQL Injection in Proxy API key verification |
No CVSS v3.0
No CVSS v2
This CVE is in the KEV database since May 8, 2026.
Exploit prediction score: 89.4% (89.420% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Litellm
Litellm litellm |
|
| CPEs | cpe:2.3:a:litellm:litellm:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Litellm
Litellm litellm |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
kev
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in LiteLLM. A database query used for proxy API key checks incorrectly incorporated caller-supplied key values directly into the query. This vulnerability allows an unauthenticated attacker to send a specially crafted Authorization header to any Large Language Model (LLM) API route, exploiting the proxy's error-handling path. Successful exploitation could enable the attacker to read and potentially modify data within the proxy's database, leading to unauthorized access to the proxy and its managed credentials. | 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. |
| Title | LiteLLM: LiteLLM: Unauthorized data access and modification via SQL injection | LiteLLM: SQL injection in Proxy API key verification |
| References |
| |
| Metrics |
cvssV4_0
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Berriai
Berriai litellm |
|
| Vendors & Products |
Berriai
Berriai litellm |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in LiteLLM. A database query used for proxy API key checks incorrectly incorporated caller-supplied key values directly into the query. This vulnerability allows an unauthenticated attacker to send a specially crafted Authorization header to any Large Language Model (LLM) API route, exploiting the proxy's error-handling path. Successful exploitation could enable the attacker to read and potentially modify data within the proxy's database, leading to unauthorized access to the proxy and its managed credentials. | |
| Title | LiteLLM: LiteLLM: Unauthorized data access and modification via SQL injection | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|