CVE-2026-59822 affects BerriAI LiteLLM versions prior to 1.84.0. The vulnerability is in LiteLLM's MCP Streamable HTTP endpoint. An unauthenticated attacker can send a fabricated Authorization header that triggers an OAuth2 passthrough fallback path. In the vulnerable logic, failed LiteLLM key validation is replaced with an empty UserAPIKeyAuth() object, allowing the request to proceed to MCP tooling without a valid LiteLLM API key. In effect, the endpoint can be reached through an authentication-bypass condition caused by improper handling of failed authentication during OAuth2 passthrough fallback.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.