Unauthenticated MCP tool access via OAuth2 fallback
Published Jul 8, 2026 · Updated Jul 8, 2026
Authentication bypass in BerriAI LiteLLM before 1.84.0 allows remote attackers to access configured MCP tools with a fabricated bearer token. MCPRequestHandler.process_mcp_request treats failed LiteLLM key validation as OAuth2 passthrough and substitutes an empty UserAPIKeyAuth object. A network-reachable Streamable HTTP MCP route and a configured MCP server are required; successful requests can list or call tools and access connected services.
Summary
What happened
Authentication bypass in BerriAI LiteLLM before 1.84.0 allows remote attackers to access configured MCP tools with a fabricated bearer token. MCPRequestHandler.process_mcp_request treats failed LiteLLM key validation as OAuth2 passthrough and substitutes an empty UserAPIKeyAuth object. A network-reachable Streamable HTTP MCP route and a configured MCP server are required; successful requests can list or call tools and access connected services.
The record
- CVE
- CVE-2026-59822
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-287, CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.84.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo