CVE-2026-42208: BerriAI LiteLLM SQL Injection Vulnerability

CISA Known Exploited Vulnerabilities

Name

BerriAI LiteLLM SQL Injection Vulnerability

Vendor

BerriAI

Product

LiteLLM

Added to the catalog

2026-05-08

Due date for US federal agencies

2026-05-11

Weaknesses

CWE-89

Catalog version

2026.10.30

BerriAI LiteLLM contains a SQL injection vulnerability that allows an attacker to read data from the proxy's database and potentially modify it, leading to unauthorized access to the proxy and the credentials it manages.

Required action (CISA)

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Ransomware use: CISA does not mark known use of this vulnerability in ransomware campaigns.

Links in CISA's notes

• https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc
• https://nvd.nist.gov/vuln/detail/CVE-2026-42208

Read on 2026-11-02T23:39:54.475Z under licence cisa-kev-cc0@b0067899 from https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json

NVD analysis

Status

Analyzed

Published

2026-05-08T04:16:19.923

Last modified

2026-10-26T20:10:00.160

Weaknesses

CWE-89

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.

References

• https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable (Product, Release Notes)
• https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc (Mitigation, Patch, Vendor Advisory)
• https://access.redhat.com/security/cve/CVE-2026-42208 (Third Party Advisory)
• https://bugzilla.redhat.com/show_bug.cgi?id=2463965 (Mitigation, Third Party Advisory)
• https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42208.json (Third Party Advisory)
• https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42208 (US Government Resource)

This product uses the NVD API but is not endorsed or certified by the NVD.

Read on 2026-11-02T23:42:31.494Z under licence nvd-api-terms-of-use@ff2a5288 from https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-42208

CVE record

Title (CNA)

LiteLLM: SQL injection in Proxy API key verification

Assigner

GitHub_M

State

PUBLISHED

Published

2026-05-08T03:38:14.124Z

Updated

2026-07-15T00:58:03.861Z

Problem types

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

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.

References

• https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc
• https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable

Read on 2026-11-03T02:20:06.141Z under licence cve-terms-of-use@81bfa2f3 from https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/42xxx/CVE-2026-42208.json

GitHub Advisory Database

Also known as / affected packages

Defensive techniques (MITRE D3FEND)

D3FEND maps these defensive techniques to the weakness (CWE) that NVD lists for this CVE, through the digital artifacts the weakness affects. D3FEND does not say they stop this vulnerability.

MITRE D3FEND™ knowledge graph. © 2025 The MITRE Corporation.
"The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use D3FEND for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy." Terms: https://d3fend.mitre.org/tou/