Quick answers
- Is CVE-2026-49468 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49468 being exploited in the wild.
- How severe is CVE-2026-49468?
- Critical severity, with a CVSS score of 4, published 22 June 2026.
- Which products and versions are affected?
- Berriai LiteLLM < 1.84.0; litellm (PyPI) ECOSYSTEM:introduced=0,fixed=1.84.0.
- Is there a fix for CVE-2026-49468?
- Yes. litellm (PyPI): upgrade to 1.84.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49468 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-49468?
- Check whether you run Berriai LiteLLM or litellm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- litellm (PyPI): upgrade to 1.84.0 or later
pip install "litellm>=1.84.0"
Technical details
An authentication bypass vulnerability exists in LiteLLM due to a Host-header parsing flaw in the `get_request_route()` function within `litellm/proxy/auth/auth_utils.py`. The authentication layer derives the effective route from `request.url.path`, which is reconstructed by the Starlette framework using the user-supplied Host header. By crafting a specific Host header, an attacker can cause the authentication gate to evaluate a different route than the one actually dispatched by FastAPI. This allows unauthenticated attackers to reach protected management endpoints. The vulnerability is mitigated if the proxy is deployed behind a WAF, CDN, or reverse proxy that validates or normalizes the Host header. The issue is fixed in version 1.84.0.
Affected products
- BerriAI litellm < 1.84.0
Identifiers
- CVE-2026-49468
- GHSA-4xpc-pv4p-pm3w
- PYSEC-2026-388
Timeline
- 2026-05-14: patched: Version 1.84.0 released
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-06-22: disclosed: CVE published to NVD