Unpatched Starlette Host Header Flaw Enables Unauthenticated RCE in LiteLLM
Written by AI from the linked story. Not reviewed by an editor. How this works
Attackers actively exploited CVE-2026-42271 and CVE-2026-48710 within days of disclosure, targeting Starlette versions prior to 1.0.1 that fail to validate the Host header. This oversight allowed adversaries to bypass access controls on a sensitive endpoint and achieve remote code execution without any authentication. The speed of exploitation underscores the critical importance of patching internet-facing AI/LLM infrastructure promptly. Notably, attackers modified payloads with unusual characters (e.g., brackets) to evade WAF signatures, demonstrating that WAF rules alone are insufficient without underlying patches. Organizations running LiteLLM or any Starlette-based service must treat this as a high-severity, time-sensitive patching event.
Tactical Insight
Immediate actions
- Upgrade Starlette to version 1.0.1 or later and redeploy all dependent services including LiteLLM immediately
- Restrict public access to sensitive endpoints such as `/mcp-rest/test/tools/list` via firewall rules or API gateway policies
Detection measures
- Review logs for anomalous Host header values or unusual characters (brackets, encoded sequences) in requests to Starlette-based services
- Deploy or update IDS/IPS signatures to flag CVE-2026-42271 and CVE-2026-48710 exploitation patterns, accounting for payload obfuscation techniques
Long-term improvements
- Integrate automated vulnerability scanning into CI/CD pipelines so newly disclosed CVEs in dependencies like Starlette are flagged before deployment
- Maintain a software bill of materials (SBOM) for all services to rapidly identify and prioritize affected instances when new CVEs emerge
- Implement strict input validation and Host header enforcement at the application layer as a defense-in-depth measure independent of WAF coverage