CriticalGHSA-4xpc-pv4p-pm3wCVE-2026-49468PYSEC-2026-388

LiteLLM: Authentication Bypass via Host Header Injection

Published 16 Jun 2026 · Updated 10 Sept 2026

Is your project on an affected litellm?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.84.0
Fixed in
1.84.0
Update to the fixed version for your release line, for example:pip install 'litellm>=1.84.0'

Details

Impact

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 litellm/proxy/auth/auth_utils.py::get_request_route(), which Starlette reconstructs from the Host header. A crafted Host 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 server_name allowlists
  • a host-based load balancer

LiteLLM Cloud customers are not affected.

Patches

Fixed in 1.84.0. Upgrade to 1.84.0 or later. No configuration change is required.

Workarounds

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.

References

Discovery Credit: Le The Thang (KCSC) and Kim Ngoc Chung (One Mount Group)

Is GHSA-4xpc-pv4p-pm3w in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected litellm, and gives you the command that fixes it.

More advisories for litellm

  • HighGHSA-g5ff-637f-6q2mLiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials` · 27 Oct 2026
  • MediumGHSA-hhww-mrg2-969hLiteLLM vulnerable to reflected XSS in /sso/debug/callback · 27 Oct 2026
  • HighCVE-2026-114612LiteLLM: Privilege Escalation to Proxy Admin via Cross-Domain Reuse of the Salt Key · 27 Oct 2026
  • MediumCVE-2026-84377LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters · 30 Sept 2026
  • MediumCVE-2026-59823LiteLLM Proxy has server-side request forgery via the `user_config` request parameter · 17 Sept 2026
  • CriticalCVE-2026-37004LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint · 27 Aug 2026
All 45 advisories for litellm

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.