High [CVE-2026-49468] Authentication Bypass via Host Header Injection
This high-severity Red Hat Linux advisory covers CVE-2026-49468 affecting Exploit Intelligence, Red Hat Ansible Automation Platform 2, Red Hat OpenShift AI (RHOAI).
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
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. A remote attacker could exploit a Host-header parsing vulnerability in the proxy authentication layer.
By sending a crafted Host header, an attacker could gain unauthenticated access to protected management routes, potentially leading to full system compromise. The vulnerability is rated with Important severity due to the limited attack surface in our default deployment configuration.
While the affected images ship with a vulnerable version of litellm, the specific vulnerability is restricted solely to proxy management-route authentication. By default, these images do not start the LiteLLM proxy server.
Instead, the default entrypoints are configured to run OGX, the MLflow server (with the AI Gateway disabled), Garak evaluation jobs, or Lightspeed/Llama Stack APIs.
- < 1.84.0
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation checklist
- To mitigate the risk of unauthenticated access, restrict network access to the LiteLLM proxy's management routes. Configure network firewalls or security groups to permit inbound connections only from trusted internal networks. This operational control limits the exposure of vulnerable endpoints to unauthorized external access. If the LiteLLM proxy is deployed behind a load balancer or API gateway, ensure these components are configured to strictly validate and sanitize the HTTP Host header before forwarding requests.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.