Server-side Request Forgery (SSRF) Affecting litellm package, versions [,1.84.0.dev2)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-LITELLM-17391910
- published21 Jun 2026
- disclosed21 Jun 2026
- creditEdward-x
Introduced: 21 Jun 2026
NewCVE-2026-12774 (opens in a new tab)How to fix?
Upgrade litellm to version 1.84.0.dev2 or higher.
Overview
litellm is a Library to easily interface with LLM API providers
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the /v1/mcp/test/connection endpoint. An attacker can perform server-side request forgery (SSRF) by supplying a crafted token_url and arbitrary Machine-to-Machine (M2M) credentials to the connection testing endpoint. Due to incomplete validation of OAuth M2M flows, the proxy issues HTTP POST requests to attacker-controlled destinations, allowing internal network reconnaissance and potentially triggering unauthorized actions on reachable services.
Note: Exploitation requires an authenticated user with access to the /v1/mcp/test/connection (or /mcp-rest/test/connection) endpoint.