LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Known exploitedUpdated
Discuss exposureBack to CVEs
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

LiteLLM proxy versions 1.81.16 through before 1.83.7 have a critical SQL injection in API key checking. An unauthenticated attacker reaching LLM API routes could access or potentially change proxy database data, including credentials the proxy manages. Version 1.83.7 contains the patch.

Executive priority

Treat this as urgent for any LiteLLM proxy in scope. It is critical, unauthenticated, KEV-listed, and can affect both confidentiality and integrity of AI gateway data and credentials.

Technical view

The proxy API key verification query incorporated the caller-supplied Authorization key into SQL text instead of binding it as a parameter. The path is reachable through LLM API route error handling. The issue is CWE-89 with CVSS 9.8, affecting BerriAI LiteLLM >=1.81.16 and <1.83.7.

Likely exposure

Exposure is likely where LiteLLM proxy deployments in the affected version range accept traffic to LLM API routes, especially internet-facing gateways or shared internal AI gateways.

Exploitation context

CISA KEV status indicates known exploitation. The provided sources do not describe attacker groups, exploit volume, or campaign details, so operational context is incomplete.

Researcher notes

The bundle names BerriAI LiteLLM only and provides no CPEs. The patch is identified as 1.83.7. Avoid assuming exploit mechanics beyond SQL injection via Authorization handling and the documented route reachability.

Mitigation direction

  • Upgrade LiteLLM proxy to version 1.83.7 or later.
  • Restrict network access to LiteLLM proxy routes until upgraded.
  • Review vendor advisory and release notes for deployment-specific guidance.
  • Rotate managed credentials if compromise is suspected.
  • Monitor proxy and database logs for unusual authorization errors or data changes.

Validation and detection

  • Inventory all LiteLLM proxy deployments and confirm exact versions.
  • Check whether affected proxies expose LLM API routes to untrusted networks.
  • Verify the deployed version is 1.83.7 or later.
  • Review logs for malformed Authorization headers and related database errors.
  • Check proxy database records for unexpected keys, users, or configuration changes.
Prepared
Reviewed
Confidence
high
Sources
7

Public sources used

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-42208 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
7Timeline events
2ADP providers
7Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9redhat-SADP
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-42208Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. ADP timelineredhat-SADP

    Reported to Red Hat.

  4. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  5. ADP timelineCISA-ADP

    CVE-2026-42208 added to CISA KEV

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvcother:kev
  • 2026-05-08T00:00:00.000Z: CVE-2026-42208 added to CISA KEV
redhat-SADPLiteLLM: LiteLLM: Unauthorized data access and modification via SQL injection
other:Red Hat severity ratingcvssV3_1
  • 2026-04-29T22:15:41.713Z: Reported to Red Hat.
  • 2026-04-28T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BerriAIlitellm>= 1.81.16, < 1.83.7Listed
Weakness

CWE details

CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs