Advisory record · GHSA-r75f-5x8p-qvmc

LiteLLM has SQL Injection in Proxy API key verification

CVSS 9.3 CriticalCriticalIn CISA KEVEPSS 0.89 · 99th percentile

Critical, because:

  • In CISA’s KEV catalogue since 8 May 2026: it is known to be exploited.
  • CVSS score 9.3: 9.0 or more.
  • CVSS score 9.3 (7.0 or more) and EPSS 0.89 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 24 Apr 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
litellmPyPI>=1.81.16, <1.83.71.83.7
Identifiers
GHSA-r75f-5x8p-qvmc · CVE-2026-42208 · PYSEC-2026-391
Weakness (CWE)
CWE-89
Published
24 Apr 2026
Updated
5 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

LiteLLM versions 1.81.16 up to but not including 1.83.7 are vulnerable to SQL injection in the proxy's API key verification. An unauthenticated attacker can send a crafted Authorization header to any LLM API route, such as POST /chat/completions, and may read data from the proxy's database and possibly modify it. Upgrade to LiteLLM 1.83.7 or later; if that is not immediately possible, set disable_error_logs to true under general_settings.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 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 CNA (GitHub_M)
  • CISA KEV Listed since 8 May 2026: known to be exploited.
  • EPSS 0.89, the 99th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.