Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
UnratedPublic exploit

SSRF in BerriAI LiteLLM MCP Server Connection Testing

IdentifiersCVE-2026-12774CWE-918

CVE-2026-12774 is a server-side request forgery vulnerability in BerriAI LiteLLM affecting versions up to and including 1.82.2. The issue is reported in the MCP Server Connection Testing component, specifically in the _execute_with_mcp_client function within litellm/proxy/_experimental/mcp_server/rest_endpoints.py. An attacker can manipulate input handled by this function to cause the LiteLLM server to initiate attacker-controlled requests to arbitrary internal or external destinations. The vulnerability is remotely exploitable, and public exploit disclosure has been reported.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to induce the vulnerable LiteLLM instance to send network requests on the attacker's behalf. This can be used to probe or access internal network services not otherwise reachable externally, interact with cloud metadata or other sensitive endpoints, bypass network segmentation assumptions, and potentially retrieve sensitive information depending on reachable targets and response handling. At minimum, it enables unauthorized server-side network interaction and internal resource enumeration.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is available, restrict or disable the MCP Server Connection Testing functionality, especially if it is exposed to untrusted users or networks. Apply strict outbound egress filtering from the LiteLLM host or container to block access to internal address space, link-local addresses, cloud metadata services, and other sensitive destinations. Where possible, enforce allowlists for reachable MCP endpoints, isolate the service in a constrained network segment, and monitor for anomalous outbound requests originating from the LiteLLM process.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release once one is made available. The provided advisory states that all versions up to and including 1.82.2 are affected and does not specify a fixed version. Review vendor release notes and security advisories for the first patched version, then update affected deployments promptly.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BerriAILitellmapplication
LitellmLitellmapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.