What Changed
BerriAI’s LiteLLM gateway, used to proxy OpenAI-compatible and multi-provider LLM traffic, contained an improper authentication flaw in its Model Context Protocol (MCP) Streamable HTTP path. In versions before 1.84.0, a failed LiteLLM API-key check on an Authorization: Bearer … header could fall through an OAuth2-passthrough branch that substituted an empty UserAPIKeyAuth() object instead of failing closed.
The result: an unauthenticated caller with an arbitrary Bearer token could establish an authenticated MCP session and reach configured MCP tooling. CISA added CVE-2026-59822 to KEV on September 2, with a federal remediation deadline of September 16. The 1.84.0 fix gates passthrough on actual target-server OAuth2 configuration and fails closed when servers cannot be resolved or are not in OAuth2 mode.
Why This Matters Operationally
LiteLLM often sits in front of production model keys, tool connectors, and internal MCP servers that can read tickets, query databases, or trigger automations. Later authorization checks treat the empty auth object as a validated session. In practice, any Bearer string could reach the MCP tools behind the gateway on versions before 1.84.0.
Know what matters before your first meeting.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
What Defenders Should Verify First
- Upgrade LiteLLM to 1.84.0 or later everywhere the proxy runs—containers, serverless functions, and laptop-side gateways that still touch production tools.
- Until patched: disable or firewall
/mcproutes and require network authentication in front of the gateway. - Audit MCP access logs for Bearer tokens that never matched a real LiteLLM key, especially around disclosure and KEV dates.
- Rotate LLM provider keys, MCP tool credentials, and any secrets reachable from configured tools if the endpoint was exposed.
- Inventory shadow LiteLLM deployments—data science and application teams stand them up faster than asset lists update.
Source Context
- CISA KEV September 2, 2026 (CVE-2026-59822)
- SentinelOne: LiteLLM auth bypass technical summary
- TechGines: LiteLLM MCP empty-object fallback
- Corgea: MCP Streamable HTTP auth bypass write-up
Upgrade past 1.84.0, lock down /mcp, and assume any exposed gateway minted sessions you did not intend.
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Best AI Security Certifications (2026): Which One Fits Your Role
The AI security certifications worth your time in 2026, checked against each issuer: CompTIA SecAI+, ISACA AAISM, GIAC GAIPS, GOAA and GASAE,...
How to Develop a Data Destruction Policy
Retired laptops, servers and drives can hold sensitive records long after they leave service. Here's how to build a data destruction policy...
CISSP vs CISM (2026): Which Security Leadership Cert Is Right?
CISSP vs CISM in 2026: exam formats, domains, experience rules, current costs and annual fees, DoD 8140 roles, salary data and which...
Friday’s brief: GitLab’s 10.0 fix, then VeloCloud attacks, a poisoned LiteLLM release and PHP2Shell logs to check
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.