CVE-2026-49468 json
LiteLLM: Authentication Bypass via Host Header Injection
published 2026-06-16 4 mo ago modified 2026-10-25 14 d ago also GHSA-4xpc-pv4p-pm3w , PYSEC-2026-388 , EUVD-2026-38361
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- pypi litellm 1.84.0
- litellm litellm 1.84.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-49468 updated cvss 8.1
litellm: LiteLLM: Authentication Bypass via Host Header Injection
-
Red Hat Exploit Intelligence exploit-intelligence-tech-preview/vulnerability-analysis-rhel9affected: workaround, no fix available
-
Red Hat Ansible Automation Platform 2 ansible-automation-platform-26/lightspeed-chatbot-rhel9, ansible-automation-platform-27/lightspeed-chatbot-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-llama-stack-core-rhel9, rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
3.03% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template LiteLLM Proxy < 1.84.0 - Host Header Authentication Bypass nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.5 | 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 |
| CISA ADP | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 9.5 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | litellm | <1.84.0 |
1.84.0 |
Affected products
- BerriAI litellm
- Red Hat Exploit Intelligence
- Red Hat Red Hat Ansible Automation Platform 2
- Red Hat Red Hat OpenShift AI (RHOAI)
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
github.com
/BerriAI/litellm/security/advisories/GHSA-4xpc-pv4p-pm3w
web, mitigation, patch, vendor-advisory
-
github.com
/BerriAI/litellm/releases/tag/v1.84.0
web, product, release-notes
-
access.redhat.com
/security/cve/CVE-2026-49468
vdb-entry, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2491520
issue-tracking, web
-
security.access.redhat.com
/data/csaf/v2/vex/2026/cve-2026-49468.json
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-49468
advisory
-
github.com
/BerriAI/litellm
package
-
github.com
/advisories/GHSA-4xpc-pv4p-pm3w
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-388.yaml
web
-
pypi.org
/project/litellm
web, package
Sources
- CVE List CVE-2026-49468
- GitHub Advisory GHSA-4xpc-pv4p-pm3w
- NVD CVE-2026-49468
- OSV PYSEC-2026-388
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.