https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 01:49:33 +0000 https://db.gcve.eu/vuln/ghsa-4xpc-pv4p-pm3w <p><strong>Affected:</strong> PyPI: litellm</p> <p>### Impact</p> <p>A Host-header parsing flaw in the LiteLLM proxy could, under specific conditions, allow unauthenticated access to protected management routes.</p> <p>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.</p> <p>**Most deployments are not affected.** The bypass is blocked by any upstream layer that validates or normalizes `Host`, such as:</p> <p>- a CDN or WAF, such as Cloudflare - a reverse proxy with `server_name` allowlists - a host-based load balancer</p> <p>**LiteLLM Cloud customers are not affected.**</p> <p>### Patches</p> <p>Fixed in **`1.84.0`**. Upgrade to `1.84.0` or later. No configuration change is required.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>- Patched release: [`v1.84.0`](https://github.com/BerriAI/litellm/releases/tag/v1.84.0)</p> <p>**Discovery Credit**: Le The Thang (KCSC) and Kim Ngoc Chung (One Mount Group)</p> <p><strong>Affected:</strong> PyPI: litellm</p> <p>### Impact</p> <p>A Host-header parsing flaw in the LiteLLM proxy could, under specific conditions, allow unauthenticated access to protected management routes.</p> <p>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.</p> <p>**Most deployments are not affected.** The bypass is blocked by any upstream layer that validates or normalizes `Host`, such as:</p> <p>- a CDN or WAF, such as Cloudflare - a reverse proxy with `server_name` allowlists - a host-based load balancer</p> <p>**LiteLLM Cloud customers are not affected.**</p> <p>### Patches</p> <p>Fixed in **`1.84.0`**. Upgrade to `1.84.0` or later. No configuration change is required.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>- Patched release: [`v1.84.0`](https://github.com/BerriAI/litellm/releases/tag/v1.84.0)</p> <p>**Discovery Credit**: Le The Thang (KCSC) and Kim Ngoc Chung (One Mount Group)</p> https://db.gcve.eu/vuln/ghsa-4xpc-pv4p-pm3w