Security Digest · Vulnerability record · Known exploited
CVE-2026-42208: BerriAI LiteLLM SQL Injection Vulnerability
Exploited in the wild (CISA KEV). LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format.
CISA KEV · added 2026-05-08 CVSS 9.3 Critical EPSS 5.8% · p93 Patch this week
Should you act?
Exploited: patch now if you run it
CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Yes, if you run BerriAI LiteLLM. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-05-08, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-05-11; treat that as the outer limit, not the target.
- EPSS 5.8%, percentile 93: FIRST’s model estimates a 5.8% chance of exploitation activity in the next 30 days, higher than 93% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
litellm(PyPI) >= 1.81.16, < 1.83.7, fixed in 1.83.7. Check your lockfile, including transitive dependencies. - Editorial verdict: Patch this week. LiteLLM Proxy: Three Exploited Flaws in CISA KEV — If you run a self-hosted LiteLLM Proxy older than 1.84.0, upgrade now and treat the provider keys it holds as possibly exposed; SDK-only users are not affected.
What it is
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.
From the GitHub advisory
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.
CISA’s summary
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.
Weakness type: CWE-89.
Product: BerriAI LiteLLM · Assigned by: GitHub_M · Published: 2026-05-08
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | litellm | >= 1.81.16, < 1.83.7 | 1.83.7 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| BerriAI | litellm | >= 1.81.16, < 1.83.7 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 4.0 | 9.3 Critical | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| redhat-SADP | 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: added 2026-05-08; federal due date 2026-05-11. Known ransomware use: Unknown.
- CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- CISA SSVC assessment: exploitation active, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 5.77% probability of exploitation activity in the next 30 days; percentile 93.
Timeline
- — GitHub-reviewed advisory GHSA-r75f-5x8p-qvmc published (critical)
- — Added to CISA’s Known Exploited Vulnerabilities catalog
- — CVE record published by GitHub_M
- — CISA remediation deadline for US federal agencies
- — CVE record last updated
- — erroneo.us brief: LiteLLM Proxy: Three Exploited Flaws in CISA KEV
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- Listed in CISA KEV notes (github.com) github.com
Vulnerability records
- GitHub Advisory GHSA-r75f-5x8p-qvmc github.com
- CVE.org record CVE-2026-42208 cve.org
- NVD entry CVE-2026-42208 nvd.nist.gov
Government
Other references from the CVE record and advisory
- github.com github.com
- access.redhat.com access.redhat.com
- RHBZ#2463965 bugzilla.redhat.com
- security.access.redhat.com security.access.redhat.com
- github.com github.com
- github.com github.com
- pypi.org pypi.org
All exploited BerriAI vulnerabilities · Critical PyPI advisories · Today’s Security Digest