CVE-2026-42208Known exploitationPublic exploitNetwork attack vector

Unauthenticated database reading and modification via SQL injection

Published May 8, 2026 · Updated May 8, 2026

SQL injection in the LiteLLM proxy 1.81.16 through 1.83.6 allows remote attackers to read or modify its database via an Authorization header. The proxy API key check interpolates the caller-supplied key into SQL instead of passing it as a separate database parameter. No credentials or user interaction are required; any LLM API route reaches the query through the error-handling path, exposing proxy data and managed credentials to unauthorized access or modification.

CVSS severity9.3
Critical
EPSS probability89.42%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SQL injection in the LiteLLM proxy 1.81.16 through 1.83.6 allows remote attackers to read or modify its database via an Authorization header. The proxy API key check interpolates the caller-supplied key into SQL instead of passing it as a separate database parameter. No credentials or user interaction are required; any LLM API route reaches the query through the error-handling path, exposing proxy data and managed credentials to unauthorized access or modification.

The record

CVE
CVE-2026-42208
Published
May 8, 2026
Updated
May 8, 2026
Vendor
Berri AI
Product
LiteLLM
Classifications
CWE-89, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 8, 2026Exploitation reportedCISA Known Exploited Vulnerabilities catalog listing
  2. May 8, 2026CVE publishedPublication date reported by the CVE source.
  3. May 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.81.16, < 1.83.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Berri AI · LiteLLMversion=>= 1.81.16, < 1.83.7

Published CVSS scores

9.8Red Hat Product SecurityCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.3GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo