How severe is CVE-2026-42208?

No CVSS score has been assigned to CVE-2026-42208 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-42208?

CVE-2026-42208 affects the following packages: litellm (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-42208?

Update litellm to 1.83.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42208 is resolved across your whole dependency graph.

How do I detect CVE-2026-42208 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-42208 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2026-42208 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-42208 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-42208?

CVE-2026-42208 has an EPSS (Exploit Prediction Scoring System) score of 5.8%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2026-42208 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-42208 (BerriAI LiteLLM SQL Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-05-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-05-11. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-42208?

CVE-2026-42208 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2026-42208?

A Nuclei detection template exists for CVE-2026-42208, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-42208 published, and has it been updated?

CVE-2026-42208 was published on May 8, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-42208 — litellm

CVE-2026-42208 is a SQL Injection vulnerability in litellm. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-05-08) — treat it as actively exploited and patch now. A fix is available for litellm — see the affected versions and patch details below.

LiteLLM: SQL injection in Proxy API key verification

Also known asGHSA-r75f-5x8p-qvmcPYSEC-2026-391

Published

May 8, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-05-08. Federal agencies were required to remediate by 2026-05-11.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-42208.

EPSS Exploitation Probability

via FIRST.org ↗

5.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍litellm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Workarounds

If upgrading is not immediately possible, set disable_error_logs: true under general_settings. This removes the path through which unauthenticated input reaches the vulnerable query.

References

Patched release: v1.83.7-stable

Discovery Credit: Tencent YunDing Security Lab

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`litellm`	≥ 1.81.16&&< 1.83.7	1.83.7`pip install --upgrade 'litellm==1.83.7'`

Affected Products

1 product · 1 configurations

Application

litellmlitellm

≥ 1.81.16 && < 1.83.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update litellm to 1.83.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42208 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect CVE-2026-42208

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-42208 -u https://target

Template: LiteLLM - SQL Injection
Severity: critical
Impact: Unauthenticated attackers can read and modify proxy database, leading to unauthorized access and credential compromise.
Remediation: Upgrade to version 1.83.7 or later.

Template by ProjectDiscovery nuclei-templates (HAERIN-L), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### 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