CVE-2026-42208: Litellm SQL Injection Vulnerability

CRITICAL
Advisory Identifier: GHSA-r75f-5x8p-qvmc
Share
CVSS 9.8
CWE-89
Published
Advisory Summary

CVE-2026-42208 is a CRITICAL (CVSS 9.8) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Litellm libraries in the PyPI ecosystem. The issue involves litellm has sql injection in proxy api key verification. Remediation is available by upgrading affected packages to version 1.83.7.

CVE-2026-42208 at a Glance

CVE Identifier CVE-2026-42208
GHSA Identifier GHSA-r75f-5x8p-qvmc
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Litellm
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-42208

To remediate this vulnerability, upgrade all affected Litellm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

litellm fixed: 1.83.7 
pip install litellm>=1.83.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show litellm

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-42208, inspect your installed packages using pip:

pip show litellm

Analyze the terminal output to locate any version of Litellm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.83.7), your application is affected.

Note: The pip show litellm command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Litellm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable) **Discovery Credit**: Tencent YunDing Security Lab

CVE-2026-42208 Affected Litellm Versions

1 component(s)
Fixed Versions:
1.83.7
Product / Package Ecosystem Affected Versions Fixed Version
litellm
pypi/litellm
PyPI
≥ 1.81.16
< 1.83.7
1.83.7

References

GitHub Advisory / Wiki ADVISORY
https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc
NVD — CVE-2026-42208 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-42208
Litellm Security Information SECURITY
https://access.redhat.com/security/cve/CVE-2026-42208
bugzilla.redhat.com/show_bug.cgi WEB
https://bugzilla.redhat.com/show_bug.cgi?id=2463965
Litellm Source Repository REPOSITORY
https://github.com/BerriAI/litellm
Litellm Release RELEASE
https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable
GitHub Advisory / Wiki ADVISORY
https://github.com/advisories/GHSA-r75f-5x8p-qvmc
Litellm Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-391.yaml
pypi.org/project/litellm WEB
https://pypi.org/project/litellm
www.cisa.gov/known-exploited-vul... WEB
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42208

Frequently Asked Questions

What is CVE-2026-42208?
CVE-2026-42208 is a security vulnerability in Litellm involving LiteLLM has SQL Injection in Proxy API key verification under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Litellm versions are affected?
Affected versions include releases prior to 1.83.7 across affected packages: litellm.
What version fixes CVE-2026-42208?
Upgrading to 1.83.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is litellm affected?
Yes, litellm is affected in releases prior to 1.83.7. Upgrade your dependency to 1.83.7 or later.
What is the CVSS score of CVE-2026-42208?
CVE-2026-42208 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-42208?
CVE-2026-42208 is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.).
How can I check PyPI dependencies for CVE-2026-42208?
Run the dependency tree command: 'pip show litellm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r75f-5x8p-qvmc",
  "modified" : "2026-10-05T18:39:54Z",
  "published" : "2026-04-24T16:17:07Z",
  "aliases" : [ "CVE-2026-42208" ],
  "summary" : "LiteLLM has SQL Injection in Proxy API key verification",
  "details" : "### Impact\n\nA 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.\n\nAn 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.\n\n### Patches\n\nFixed 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.\n\n### Workarounds\n\nIf 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.\n\n### References\n\n- Patched release: [`v1.83.7-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable)\n\n**Discovery Credit**: Tencent YunDing Security Lab",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "litellm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.81.16"
      }, {
        "fixed" : "1.83.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42208"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-42208"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2463965"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/BerriAI/litellm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-r75f-5x8p-qvmc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-391.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/litellm"
  }, {
    "type" : "WEB",
    "url" : "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42208"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-89" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-24T16:17:07Z",
    "nvd_published_at" : "2026-05-08T04:16:19Z"
  }
}