CVE-2026-59822 is an improper authentication vulnerability in BerriAI LiteLLM versions before 1.84.0. The MCP Streamable HTTP endpoint accepts a fabricated Authorization header that triggers an OAuth2 passthrough fallback path. When LiteLLM key validation fails, this path substitutes an unrestricted empty UserAPIKeyAuth() object rather than rejecting the request. Consequently, an attacker can reach MCP tooling without presenting a valid LiteLLM key.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authentication-bypass flaw in LiteLLM's MCP Gateway that could allow MCP functions to accept a one-character bearer token, enabling unauthorized access to exposed AI-agent tooling.
An authentication-bypass vulnerability in LiteLLM's MCP Gateway that permits unrestricted MCP access using an invalid or minimal Bearer token.
An authentication bypass vulnerability in the LiteLLM MCP proxy referenced as real-world precedent for unauthenticated MCP tool enumeration/execution exposure.
An authentication bypass vulnerability in BerriAI LiteLLM prior to version 1.84.0 that allows unauthenticated access to MCP tooling by abusing a fabricated Authorization header and OAuth2 passthrough fallback behavior.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.