CVE-2026-42208
criticalPriorität · handeln · 90OT-Risiko · kritischKEV · ausgenutztEPSS 0.894 · 100. PerzentilExploit · funktionalDEEUNLUShinzugefügt 2026-05-08beheben bis 2026-05-11
erforderliche Maßnahme Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
EPSS · bewertet 2026-10-26
BerriAI LiteLLM SQL Injection Vulnerability
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
Exploits (7)
Öffentlicher Proof-of-Concept- und Exploit-Code.
- 0xBlackash/CVE-2026-42208CVE-2026-40487PoC · poc_in_github
- HAERIN-L/poc_cve-2026-42208HAERIN-L/poc_cve-2026-42208PoC · poc_in_github
- imjdl/CVE-2026-42208_labCVE-2026-42208 labPoC · poc_in_github
betroffene Produkte (7)
Betroffene Produkte und Versionsbereiche.
Advisories (4)
Hersteller- und Ökosystem-Meldungen dazu.
- NCSC-2026-0137Kwetsbaarheden verholpen in LiteLLM door BerriAINL2026-05-11csaf · ncsc_nlNL
BerriAI heeft kwetsbaarheden verholpen in LiteLLM, specifiek in versies 1.74.2 tot en met 1.83.6.
- WID-SEC-W-2026-1288LiteLLM: Mehrere SchwachstellenDeutsch2026-04-27csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in LiteLLM ausnutzen, um einen SQL-Injection-Angriff durchzuführen und sich unbefugten Zugriff zu verschaffen oder um beliebigen Programmcode mit den Rechten des Dienstes auszuführen
- GHSA-r75f-5x8p-qvmcLiteLLM has SQL Injection in Proxy API key verification2026-04-24ghsa · osvUS
### 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`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable) **Discovery Credit**: Tencent YunDing Security Lab
- PYSEC-2026-391LiteLLM has SQL Injection in Proxy API key verification2026-06-29vendor · osvUS
### 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`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable) **Discovery Credit**: Tencent YunDing Security Lab
auch bekannt als (6)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (10)
Externe Belege — Patches, Meldungen, Analysen.
- https://github.com/BerriAI/litellm/releasesPatchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-42208cnnvd
- https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stableenisa_euvd
- https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmcenisa_euvd
- https://access.redhat.com/security/cve/CVE-2026-42208Third Party Advisorynvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2463965MitigationThird Party Advisorynvd
- https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stableProductRelease Notesnvd
- https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmcMitigationPatchVendor Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan