Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-42208: LiteLLM: SQL injection in Proxy API key verification

CriticalCVSS 9.3 · v4.0KEVWeaponized Fix available

Noroxi assessment

Priority: Now (action score 94/100)

  • CISA has confirmed exploitation in the wild (May 8, 2026). Remediation deadline for US federal agencies: May 11, 2026.
  • A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 89.4% (FIRST EPSS); higher than 99.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: BerriAI litellm 1.83.7.

Patch today or shut off access. Upgrade to BerriAI litellm 1.83.7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

Published
May 8, 2026
Updated
Oct 26, 2026
EPSS
89.4% · 99th percentile

Report tools

JSON

Action score

94

Now

Patch today or shut off access.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
30 / 30 · Listed
EPSS
27 / 30 · 89.4%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.3
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on May 8, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: May 11, 2026.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-42208

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for litellm records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
litellmlitellm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • litellm litellm1.81.16 and later · before 1.83.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • BerriAI litellm

    • >= 1.81.16, < 1.83.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIlitellmfrom 1.81.16 · before 1.83.71.83.7

Same product

litellm: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-42271LiteLLM: Authenticated command execution via MCP stdio test endpointsKEV
    91Now
  • CVE-2026-59822LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbackKEV
    65This week
  • CVE-2026-35029LiteLLM affected by privilege escalation via unrestricted proxy configuration endpoint
    46Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-40217Apr 10, 2026 · LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
    40Plan
  • ← EarlierCVE-2026-42203May 8, 2026 · LiteLLM: Server-Side Template Injection in /prompts/test endpoint
    34Monitor
  • Later →CVE-2026-47101May 21, 2026 · LiteLLM < 1.83.14 Privilege Escalation via API Key Generation
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
BerriAI litellm1.83.7 · descriptionVendor (CNA)
PyPI:litellm1.83.7Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×6

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleauxiliary/scanner/http/litellm_proxy_sqliBerriAI LiteLLM Proxy Pre-Auth SQL Injection Scannerauxiliary2026-04-20
Nuclei detection templateNuclei template CVE-2026-42208 —
Proof-of-concept repository on GitHubstars:02026-04-28
Proof-of-concept repository on GitHubstars:02026-05-03
Proof-of-concept repository on GitHubstars:02026-05-10
Proof-of-concept repository on GitHubstars:02026-05-10
Proof-of-concept repository on GitHubstars:12026-05-22
Proof-of-concept repository on GitHubstars:02026-05-30

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-18 d
  2. First PoC-10 d
  3. CISA KEVsame day
  4. Published
  5. TodayNov 12, 2026+188 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-45809309 days apartSQL Injection vulnerability in BerriAI LiteLLM before 1.81.0 allows attackers to execute arbitrary commands via the key parameter to the…
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

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

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records