UTC
Critical

LiteLLM: Authentication Bypass via Host Header Injection

CVE-2026-49468 · GHSA-4xpc-pv4p-pm3w · published 2026-06-16 · updated 2026-07-18

Severity
Critical
CVSS score
9.8
Chance of exploitation (EPSS)
3.0%
Fixed in
1.84.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

A Host-header parsing flaw in the LiteLLM proxy could, under specific conditions, allow unauthenticated access to protected management routes. The auth layer derived the effective route from request.url.path in could therefore make the auth gate evaluate a different route from the one FastAPI dispatched. Most deployments are not affected. The bypass is blocked by any upstream layer that validates or normalizes Host, such as: a CDN or WAF, such as Cloudflare a reverse proxy with servername allowlists a host-based load balancer LiteLLM Cloud customers are not affected.**

What to do

Upgrade litellm to 1.84.0 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.84.0. Upgrade to 1.84.0 or later. No configuration change is required.

If you cannot upgrade yet

If upgrading is not immediately possible, place the proxy behind an upstream component that validates or normalizes the Host header before forwarding (a CDN/WAF, a reverse proxy with explicit server_name allowlists, or a cloud load balancer with host-based routing rules), or otherwise restrict network access to the proxy listener.

Affected
PackageRegistryAffectedFixed in
litellmPyPI< 1.84.01.84.0
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • 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].