CVE-2026-59822

Summary

LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback

Severity

high

EPSS

0.8% (p57)

CWE

CWE-287

Also known as

GHSA-7488-6r32-c95q

Published

2026-07-22

Updated

2026-07-22

Advisory 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

• v1.84.0

References

• https://github.com/advisories/GHSA-7488-6r32-c95q
• 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/releases/tag/v1.84.0

Related advisories

• CVE-2026-49468 — critical · PyPI/litellm
• CVE-2026-42208 — critical · PyPI/litellm
• CVE-2026-35030 — critical · PyPI/litellm
• GHSA-5mg7-485q-xm76 — critical · PyPI/litellm
• CVE-2026-40217 — high · PyPI/litellm
• CVE-2026-42271 — high · PyPI/litellm
• CVE-2026-42203 — high · PyPI/litellm
• GHSA-69x8-hrgq-fjj8 — high · PyPI/litellm

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Summarize with AI

ChatGPTClaudePerplexity