Critical

LiteLLM has SQL Injection in Proxy API key verification

  • Disclosed: 24.04.2026
  • Updated: 11.10.2026 15:18

CISA confirms exploitation of this vulnerability in real attacks. Prioritise checking whether your application is affected. CISA KEV · CC0 1.0

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

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) litellm >= 1.81.16, < 1.83.7 1.83.7

References

CVSS score 9.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-89
Platform
Python (PyPI)
Package
litellm
Disclosed
24.04.2026
Updated
11.10.2026 15:18

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-391 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-r75f-5x8p-qvmc - CC BY 4.0

Vulnerability history: litellm

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (42) in the archive
Total entries
42
First → latest
04.2024 09.2026
Without a fix
14
Exploited in attacks
3

Severity breakdown

  • Critical 7
  • High 17
  • Medium 8
  • Low 9
  • Unrated 1

Disclosures per year

  1. 2024: 8
  2. 2025: 6
  3. 2026: 28
Severity:
  1. High Exploited in attacks CVE-2026-59822 < 1.84.0 1.84.0
  2. Critical · 9.8 CVE-2026-49468 < 1.84.0 1.84.0
  3. High · 8.8 CVE-2026-40217 >= 1.81.8, < 1.83.10 1.83.10
  4. High · 8.8 Exploited in attacks CVE-2026-42271 >= 1.74.2, < 1.83.7 1.83.7
  5. LiteLLM has SQL Injection in Proxy API key verification this entry
    Critical · 9.8 Exploited in attacks CVE-2026-42208 >= 1.81.16, < 1.83.7 1.83.7
  6. High CVE-2026-42203 >= 1.80.5, < 1.83.7 1.83.7
  7. Critical ghsa-5mg7-485q-xm76 >= 1.82.7, <= 1.82.8 no fix
  8. High · 8.1 CVE-2025-0628 < 1.61.15 1.61.15
  9. High · 7.5 CVE-2025-0330 <= 1.52.1 no fix
  10. High · 7.5 CVE-2024-9606 < 1.44.12 1.44.12
  11. High · 8.8 CVE-2024-6825 >= 1.40.3.dev2, <= 1.40.12 no fix
  12. High · 7.5 CVE-2024-10188 < 1.53.1.dev1 1.53.1.dev1
  13. High · 7.5 CVE-2024-6587 < 1.44.8 1.44.8
Show more (4) Showing 20 of 24

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.