UTC
Medium

LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters

CVE-2026-84377 · GHSA-3cv6-jpf6-8222 · published 2026-09-30

Severity
Medium
CVSS score
6.5
Chance of exploitation (EPSS)
0.54%
Fixed in
1.96.2
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

Any authenticated LiteLLM proxy user could redirect an outbound provider call to a destination they control and cause the proxy to send its own configured provider credentials to that destination. The proxy's request-body validation was a denylist that did not cover every sensitive parameter and did not inspect parameters nested inside other request fields, so a caller could supply a routing or credential value that the proxy applied without clearing the operator's stored key. Any authenticated user could therefore exfiltrate the operator's upstream provider credentials and other configured secrets, and perform Server-Side Request Forgery against internal services reachable from the proxy.

What to do

Upgrade litellm to 1.96.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Fixed in 1.96.2, 1.95.1, 1.94.3, 1.93.2, 1.92.2, 1.91.5, 1.90.7, 1.89.7, and 1.88.6.

If you cannot upgrade yet

Set general_settings.allow_client_side_credentials to false so callers cannot override connection parameters, restrict proxy keys to trusted callers, and block the affected parameters (api_base, base_url, model_list, fallbacks, provider credential fields) at a reverse proxy or API gateway.

Affected
PackageRegistryAffectedFixed in
litellmPyPI< 1.88.61.88.6
litellmPyPI>= 1.89.0, < 1.89.71.89.7
litellmPyPI>= 1.90.0, < 1.90.71.90.7
litellmPyPI>= 1.91.0, < 1.91.51.91.5
litellmPyPI>= 1.92.0, < 1.92.21.92.2
litellmPyPI>= 1.93.0, < 1.93.21.93.2
litellmPyPI>= 1.94.0, < 1.94.31.94.3
litellmPyPI>= 1.95.0, < 1.95.11.95.1
litellmPyPI>= 1.96.0, < 1.96.21.96.2
Downstream in the Official MCP Registry

2 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • io.github.airas-org/airaslitellm@1.84.0
  • io.github.Brightdotdev/darwin-raglitellm@1.83.14
See the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].