---
schema_version: '1.0'
id: security-20260711-1179e0
url: https://osv.dev/vulnerability/PYSEC-2026-388
url_hash: 1179e00be804940b52e64bb07a5412c1461198062b4e031e503b7b75931368cc
canonical_url: https://osv.dev/vulnerability/PYSEC-2026-388
source: osv:pypa
category: security/library
category_raw: cve/library
region: null
tags:
- cve
- CVE-2026-49468
- PYSEC-2026-388
- severity:CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- litellm
- PyPI
lang: en
published_at: '2026-06-29T11:50:52Z'
fetched_at: '2026-07-11T06:37:17Z'
updated_at: '2026-07-11T06:39:11Z'
status: published
content_hash: 1ac8adfcff033b98dc7032fec3a83cfa12ed3b2e5c69da2ea30ee30fc14ee3b4
license_note: full
summary: 'LiteLLM: Authentication Bypass via Host Header Injection'
summary_source: rss
summary_en: 'LiteLLM: Authentication Bypass via Host Header Injection'
entities:
- name: VIATRIX
  type: artifact
key_facts: []
related: []
related_auto:
- name: 傲鲨
  type: organization
  weight: 1.0
title: 'CVE-2026-49468: LiteLLM: Authentication Bypass via Host Header Injection'
---

# CVE-2026-49468: LiteLLM: Authentication Bypass via Host Header Injection

## TL;DR
LiteLLM: Authentication Bypass via Host Header Injection

## Key Points
- cve / CVE-2026-49468 / PYSEC-2026-388 / severity:CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H / litellm / PyPI

## Details
**Severity:** CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
**Advisory:** PYSEC-2026-388 (CVE-2026-49468)

**Affected (your watchlist):**
- `PyPI:litellm` 1.72.6.post2 → fixed in 1.84.0 [docker/docker-strands]

**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

- Patched release: [`v1.84.0`](https://github.com/BerriAI/litellm/releases/tag/v1.84.0)
 
**Discovery Credit**: Le The Thang (KCSC) and Kim Ngoc Chung (One Mount Group)

**References:**
- https://github.com/BerriAI/litellm/security/advisories/GHSA-4xpc-pv4p-pm3w
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.84.0
- https://pypi.org/project/litellm
- https://github.com/advisories/GHSA-4xpc-pv4p-pm3w
- https://nvd.nist.gov/vuln/detail/CVE-2026-49468

_Data: OSV.dev (upstream: pypa) — https://osv.dev/vulnerability/PYSEC-2026-388_

## Source
元記事: [CVE-2026-49468: LiteLLM: Authentication Bypass via Host Header Injection](https://osv.dev/vulnerability/PYSEC-2026-388) — published 2026-06-29T11:50:52Z