Kludex Starlette did not validate the HTTP Host header when building request.url, so security checks based on it could be bypassed. CISA lists CVE-2026-48710 as exploited; the CVSS 3.1 score is 6.5 (medium).
What is affected
The vulnerability is tracked as CVE-2026-48710 and concerns Kludex Starlette, a lightweight ASGI framework and toolkit. The public sources list these affected version ranges for Starlette, exactly as published:
≥ 0.8.3, < 1.0.1≥ 3.3, < 3.3.5≥ 3.3.0, ≤ 3.3.5≥ 3.4, < 3.4.2< 8.2.0
The vendor advisory is the reference for deciding which of these ranges applies to the release you run. The weakness is classified as CWE-444 (inconsistent interpretation of HTTP requests). The issue was disclosed on 2026-05-26. The CVSS 3.1 base score is 6.5, which is a medium severity, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. This describes an attack over the network with low complexity, no privileges and no user interaction, and a limited impact on confidentiality and integrity.
What the flaw allows
According to the Starlette advisory, the HTTP Host request header was not validated before it was used to rebuild request.url. Routing relies on the raw HTTP path, while request.url is reconstructed from the Host header. A malformed header could therefore make the path in request.url differ from the path that was actually requested.
The sources state the consequence: middleware and endpoints that apply security restrictions based on request.url, rather than on the raw path in the ASGI scope, could be bypassed. Applications that do not make access decisions from request.url are not described as affected in this way, but the vendor advisory is the place to confirm this for your own code.
Exploitation
CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-09-02. CISA's stated due date of 2026-09-16 is its deadline for US federal agencies. The sources do not describe how the exploitation takes place, and this advisory does not either.
What to do
Identify the applications you run that use Starlette, directly or through another framework, and compare their versions with the affected ranges above. The Starlette security advisory lists the fixed releases and describes how the validation of the Host header was changed. Pay particular attention to middleware or endpoints in which an access restriction depends on request.url. The mitigation section below gives the sources to use.
What to do
Update Starlette to a fixed release. The Starlette security advisory lists the fixed releases. Further details are in the NVD entry for CVE-2026-48710 and the CISA Known Exploited Vulnerabilities catalogue. Check your own middleware and endpoints for security restrictions that depend on request.url.
Sources
- https://github.com/Kludex/starlette/security/advisories/GHSA-86qp-5c8j-p5mr
- https://nvd.nist.gov/vuln/detail/CVE-2026-48710
- https://github.com/Kludex/starlette/commit/764dab0dcfb9033d75442d7a359645c9f94648c6
- https://badhost.org
- https://github.com/pypa/advisory-database/tree/main/vulns/starlette/PYSEC-2026-161.yaml
- https://ostif.org/disclosing-the-badhost-vulnerability-in-starlette
- https://access.redhat.com/errata/RHSA-2026:22992
- https://access.redhat.com/errata/RHSA-2026:22993
- https://access.redhat.com/errata/RHSA-2026:23346
- https://access.redhat.com/errata/RHSA-2026:24866
- https://access.redhat.com/errata/RHSA-2026:26226
- https://access.redhat.com/errata/RHSA-2026:30088
- https://access.redhat.com/errata/RHSA-2026:30089
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog