LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback
CVE-2026-59822 · GHSA-7488-6r32-c95q · published 2026-07-22
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.84%
- Fixed in
- 1.84.0
Known exploited
CISA added this to its Known Exploited Vulnerabilities catalog on 2026-09-02; US federal agencies had until 2026-09-16 to act. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk.
- Exploitation Exploited in the wild
- Automatable Yes
- Technical impact Partial
- CISA SSVC
LiteLLM's MCP Streamable HTTP endpoint could allow an unauthenticated attacker to establish an authenticated MCP session using an arbitrary Bearer token. The MCP auth handler supported OAuth2 passthrough for upstream MCP servers, but the fallback path could replace failed LiteLLM key validation with an empty UserAPIKeyAuth() object. This allowed requests with a fabricated Authorization header to reach MCP tooling without a valid LiteLLM key. An attacker could use this to list and call configured MCP tools and access connected services exposed through MCP.
Upgrade litellm to 1.84.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue is fixed in 1.84.0. We recommend upgrading to 1.84.0 or later.
If upgrading is not immediately possible, disable MCP routes or block access to /mcp/ and related MCP endpoints at your reverse proxy or API gateway.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| litellm | PyPI | < 1.84.0 | 1.84.0 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.Brightdotdev/darwin-raglitellm@1.83.14
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- Critical[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty tokenmcp-atlassian
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalLiteLLM vulnerable to server-side template injection in the /prompts/test endpointlitellm
- CriticalMalicious code in litellm (PyPI)litellm, litellm, litellm
- CriticalLiteLLM: Authentication Bypass via Host Header Injectionlitellm
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.