Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Starlette Host Header Bypass (CVE-2026-48710)

CVE-2026-48710 is a Starlette Host header validation flaw that can bypass application checks based on the reconstructed URL path.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-48710
Vendor
Kludex
Affected Product
Starlette
Exploitation
Listed in CISA KEV
Published
2026-05-26

Starlette 1.0.0 and earlier are affected, and version 1.0.1 contains the fix. CISA added the CVE to its Known Exploited Vulnerabilities catalog on September 2, 2026.The vendor says the affected path is a security decision made from request.url or request.url.path. A route using the actual request path can behave differently from middleware reading that reconstructed URL. This distinction matters when an application protects selected paths with middleware.

What it allows

How Can CVE-2026-48710 Bypass Path Checks?

Starlette used the unvalidated Host header to reconstruct request.url while routing relied on the actual HTTP path. A malformed Host value can therefore make request.url.path differ from the path used to select an endpoint. Middleware that authorizes requests using the reconstructed path may approve a request to a protected route.

That effect depends on application code using request.url for a security decision. The vendor says a fronting proxy mitigates the issue only when it rejects or normalizes malformed Host values before forwarding. Review proxy handling and any other attacker-controlled host headers rather than assuming the proxy removes exposure.

Horizon3 reports a separate chain in vulnerable LiteLLM deployments that also contain Starlette 1.0.0 or earlier. There, the path-check bypass can remove an authentication barrier for LiteLLM CVE-2026-42271, a command injection flaw. Horizon3 validated unauthenticated command execution in that specific combination. CVE-2026-48710 alone does not establish remote code execution in every Starlette application.

CISA's September 2, 2026 KEV entry establishes known exploitation of the Starlette CVE, but it does not identify every affected application. Brandefense Blackhole counted nine dark chat posts matching CVE-2026-48710 from August 18 through November 16, 2026. The measured unit is a post, not an incident or a unique actor. A GitHub search in the November 16 source package found five public repositories naming this CVE; that count does not establish exploitation.

Use a vulnerability intelligence platform to prioritize this KEV entry alongside application exposure. The vulnerability intelligence glossary defines the signals used in triage. The vulnerability management guide explains how to track the fix and verify it.

Who is affected

Which Starlette Installations Are Affected by CVE-2026-48710?

Kludex lists Starlette versions through 1.0.0 as affected and 1.0.1 as patched. The security impact requires an application to make a sensitive decision from request.url or request.url.path. Inventory both direct and transitive Starlette dependencies, then inspect authorization middleware and endpoint checks for that pattern.

For the LiteLLM chain, Horizon3 identifies LiteLLM 1.74.2 through 1.83.6 with a dependency tree containing Starlette 1.0.0 or earlier. Confirm the installed versions of both packages and whether the affected LiteLLM functionality is reachable. A package manifest alone does not show whether the vulnerable path check is used in a given deployment.

Kludex gives an upper affected boundary but no comparable lower boundary for every historical Starlette release. The version control therefore requires a manual check against the installed package and the vendor advisory. For distributor packages, confirm the distributor's patch status before relying on an upstream version string.

Timeline

  1. 2026-05-21

    Kludex published the Starlette security advisory and identified 1.0.1 as the patched version.

  2. 2026-05-26

    NVD published the CVE-2026-48710 record.

  3. 2026-06-01

    Horizon3 says its researchers validated a chain with LiteLLM CVE-2026-42271.

  4. 2026-09-02

    CISA added CVE-2026-48710 to the Known Exploited Vulnerabilities catalog.

What to do

  1. Find affected Starlette applications

    Inventory direct and transitive Starlette dependencies. Prioritize applications running version 1.0.0 or earlier that use request.url or request.url.path for authorization or other security decisions.

  2. Patch Starlette and affected LiteLLM deployments

    Upgrade Starlette to 1.0.1 or later. For the reported LiteLLM chain, Horizon3 recommends LiteLLM 1.83.7 or later plus Starlette 1.0.1 or later.

  3. Verify the running versions and controls

    After deployment, confirm the Starlette version in the running environment, not only in a lockfile. Confirm LiteLLM's running version where applicable, and check that the proxy rejects or normalizes malformed Host values.

  4. Review activity on exposed systems

    Investigate unusual Host header handling, protected-route access and unexpected process execution on relevant LiteLLM hosts. Treat the KEV listing as evidence of exploitation, while validating any local compromise separately.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-48710?

It is a Starlette Host header validation flaw. A malformed Host value can make the reconstructed URL path differ from the routed path, bypassing application checks based on that URL.

Which Starlette version fixes CVE-2026-48710?

Kludex lists 1.0.1 as patched. Confirm that the running application actually loads version 1.0.1 or later, including when Starlette arrives through another package.

Does this CVE always give an attacker remote code execution?

No. Horizon3 validated command execution only when this bypass was chained with LiteLLM CVE-2026-42271 in a vulnerable deployment.

Is CVE-2026-48710 known to be exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on September 2, 2026. The entry does not identify every affected application or local incident.

Sources

  1. Missing Host header validation poisons request.url.pathKludex
  2. CVE-2026-42271 Chained with CVE-2026-48710Horizon3
  3. Known Exploited Vulnerabilities CatalogCISA
  4. CVE-2026-48710 DetailNVD
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →