Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48710 – Authentication Bypass – Starlette (Python ASGI Framework) prior to version 1.0.1

Summary

CVE-2026-48710, dubbed "BadHost," is a Host header authentication bypass vulnerability in Starlette, the lightweight Python ASGI framework underlying FastAPI, vLLM, LiteLLM, MCP servers, and a broad ecosystem of AI agent infrastructure. Affecting all Starlette releases from version 0.8.3 through 1.0.0, the flaw enables unauthenticated remote attackers to bypass path-based security middleware by injecting a single malformed character into the HTTP Host request header. The vulnerability was discovered by X41 D-Sec during an OSTIF-sponsored security audit of vLLM and carries a CVSS v3.1 base score of 6.5 (Medium), though security researchers assessed the real-world impact as materially more severe than the score reflects.

Technical details

  • Root cause: Starlette reconstructs request.url by concatenating the raw HTTP Host header with the request path using the pattern f"{scheme}://{host_header}{path}", without first validating the Host value against RFC 9112 3.2 or RFC 3986 3.2.2. Special characters such as /, ?, and # in the Host header shift where the path, query, and fragment boundaries are parsed in the resulting URL string.
  • Trigger conditions: Any middleware or endpoint that makes security decisions based on request.url or request.url.path — rather than the raw ASGI scope['path'] — is vulnerable. No authentication, victim interaction, or special server configuration is required.
  • Attack vector: An attacker sends an HTTP request with a crafted Host header containing a path-separator character. For example, a Host value of example.com? causes Starlette to present middleware with a sanitized allowlisted path (e.g., /health) while the underlying router dispatches the actual request to a protected endpoint (e.g., /admin). Requests returning 403 Forbidden with a normal Host header return 200 OK with a single appended ? character. A one-line curl command is sufficient to trigger the bypass; no special tooling is required.
  • Impact: Complete authentication bypass for any path-based security control implemented in Starlette middleware or endpoints. Researchers at X41 D-Sec further identified that in certain deployment patterns the bypass can chain into Server-Side Request Forgery (SSRF) against cloud metadata services, and in environments where protected endpoints expose model loading or tool execution, potentially into Remote Code Execution (RCE). Multiple public proof-of-concept exploits are available, including a dedicated online scanner at badhost.org.

Affected software

  • Starlette versions 0.8.3 through < 1.0.1
  • FastAPI (all releases depending on an affected Starlette version)
  • vLLM, LiteLLM, text-generation-inference, and other frameworks built on top of Starlette
  • MCP servers and AI agent harnesses built on Starlette-based frameworks

Severity

CVSS v3.1 Base Score: 6.5 (Medium)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Mitigation and recommended actions

  • Immediate action: Upgrade to Starlette 1.0.1 or later. Version 1.0.1 validates the Host header against RFC 9112 §3.2 / RFC 3986 §3.2.2 and falls back to scope["server"] for malformed values. FastAPI, vLLM, LiteLLM, and all dependent frameworks should be updated to releases pinned to Starlette ≥ 1.0.1. All containers and bundled virtual environments must be rebuilt and redeployed.
  • If immediate patching is not feasible:
  • Deploy a compliant reverse proxy (such as nginx or Apache) in front of the Starlette application; properly configured proxies will normalize or reject malformed Host headers before they reach Starlette.
  • Audit middleware and endpoint security logic to ensure all security decisions reference scope['path'] rather than request.url.path.
  • Restrict network access to exposed Starlette-based services where possible.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge