Vulnerability in litellm (CVE-2026-49468)
Summary
Vulnerability in litellm (CVE-2026-49468). Successful exploitation can lead to full system takeover. Exploitable via request.url.path. Mitigation: upgrade to 1.84.0 or later.
Original description
The description as published by the source.
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, 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. This vulnerability is fixed in 1.84.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49468 has been found in litellm.
Attackers can target a specific entry point like request.url.path over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade litellm to 1.84.0 or later.
If unsure, ask your IT team or search "litellm CVE-2026-49468" on the vendor's site.
CVE-2026-49468 (litellm) — CWE-290 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: request.url.path / Host / server_name
Patched: 1.84.0 — apply immediately
Workaround: 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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in litellm. Attackers reach the vulnerable code path via request.url.path without authentication.
Check the vendor advisory for the affected versions of litellm. Attack surface: request.url.path / Host / server_name.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 1.84.0.
Workaround: 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.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'litellm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'litellm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
litellmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
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.パッチが適用されるまでの応急処置として、place the proxy behind an upstream component that validates or normalizes the
Hostheader before forwarding (a CDN/WAF, a reverse proxy with explicitserver_nameallowlists, or a cloud load balancer with host-based routing rules), or otherwise restrict network access to the proxy listener. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade litellm to 1.84.0ステージング環境で 1.84.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- report bugzilla.redhat.com
- web github.com
- web security.access.redhat.com
- web github.com