Skip to content
LiteLLMGHSA-7488-6r32-c95q

LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback

HighCVE-2026-59822 · Published Jul 22, 2026 · updated Sep 10, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
litellm
PyPI
< 1.84.01.84.0
Details and references

### Impact 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. ### Patches The issue is fixed in `1.84.0`. We recommend upgrading to `1.84.0` or later. ### Workarounds 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. ### References * [v1.84.0](https://github.com/BerriAI/litellm/releases/tag/v1.84.0)

CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-287
Also known as
CVE-2026-59822, PYSEC-2026-3479

More LiteLLM advisories

All LiteLLM

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.