Browse / MCP and Tool Server Flaws / CVE-2026-59822
LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback
- Class
- MCP and Tool Server Flaws (filed by a model that read the advisory)
- Technique
- Authentication and access control
- Affected
- litellm (PyPI)
- Gets past
- Authentication check
- CVSS
- 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
- EPSS
- 0.8% chance of exploitation in 30 days
How it works, in short
An unauthenticated caller sends a fabricated Bearer token to the MCP endpoint, and a fallback path substitutes an empty auth object so the session is accepted. (Our summary, written by a model. The source text is below.)
Details
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
References
- https://github.com/BerriAI/litellm/security/advisories/GHSA-7488-6r32-c95q
- https://nvd.nist.gov/vuln/detail/CVE-2026-59822
- https://github.com/BerriAI/litellm/pull/26463
- https://github.com/BerriAI/litellm/commit/73869f0faf7d11ee21adcb5f91b8c33a340b6c2c
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.84.0
Source: GitHub Advisory Database, used under CC BY 4.0.