PYSEC-2026-161
Vulnerability from pysec - Published: 2026-05-22 13:10 - Updated: 2026-05-22 13:11Starlette reconstructs the requested URL based on the HTTP Host request header and requested path, but does not perform any validation of the Host header value. This allows attackers to inject paths into the host part, prepending the actual path. However, routing in Starlette is based on the actual request path. This inconsistent interpretation of HTTP requests may lead to issues such as authentication bypass when the authentication depends on the reconstructed URL’s path.
| Name | purl | starlette | pkg:pypi/starlette |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "starlette",
"purl": "pkg:pypi/starlette"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.1.1",
"0.1.10",
"0.1.11",
"0.1.12",
"0.1.13",
"0.1.14",
"0.1.15",
"0.1.16",
"0.1.17",
"0.1.2",
"0.1.3",
"0.1.4",
"0.1.5",
"0.1.6",
"0.1.7",
"0.1.8",
"0.1.9",
"0.10.0",
"0.10.1",
"0.10.2",
"0.10.3",
"0.10.4",
"0.10.5",
"0.10.6",
"0.10.7",
"0.11.0",
"0.11.1",
"0.11.2",
"0.11.3",
"0.11.4",
"0.12.0",
"0.12.0b1",
"0.12.0b2",
"0.12.0b3",
"0.12.1",
"0.12.10",
"0.12.11",
"0.12.12",
"0.12.13",
"0.12.2",
"0.12.3",
"0.12.4",
"0.12.5",
"0.12.6",
"0.12.7",
"0.12.8",
"0.12.9",
"0.13.0",
"0.13.1",
"0.13.2",
"0.13.3",
"0.13.4",
"0.13.5",
"0.13.6",
"0.13.7",
"0.13.8",
"0.14.0",
"0.14.1",
"0.14.2",
"0.15.0",
"0.16.0",
"0.17.0",
"0.17.1",
"0.18.0",
"0.19.0",
"0.19.1",
"0.2.0",
"0.2.1",
"0.2.2",
"0.2.3",
"0.20.0",
"0.20.1",
"0.20.2",
"0.20.3",
"0.20.4",
"0.21.0",
"0.22.0",
"0.23.0",
"0.23.1",
"0.24.0",
"0.25.0",
"0.26.0",
"0.26.0.post1",
"0.26.1",
"0.27.0",
"0.28.0",
"0.29.0",
"0.3.0",
"0.3.1",
"0.3.2",
"0.3.3",
"0.3.4",
"0.3.5",
"0.3.6",
"0.3.7",
"0.30.0",
"0.31.0",
"0.31.1",
"0.32.0",
"0.32.0.post1",
"0.33.0",
"0.34.0",
"0.35.0",
"0.35.1",
"0.36.0",
"0.36.1",
"0.36.2",
"0.36.3",
"0.37.0",
"0.37.1",
"0.37.2",
"0.38.0",
"0.38.1",
"0.38.2",
"0.38.3",
"0.38.4",
"0.38.5",
"0.38.6",
"0.39.0",
"0.39.1",
"0.39.2",
"0.4.0",
"0.4.1",
"0.4.2",
"0.40.0",
"0.41.0",
"0.41.1",
"0.41.2",
"0.41.3",
"0.42.0",
"0.43.0",
"0.44.0",
"0.45.0",
"0.45.1",
"0.45.2",
"0.45.3",
"0.46.0",
"0.46.1",
"0.46.2",
"0.47.0",
"0.47.1",
"0.47.2",
"0.47.3",
"0.48.0",
"0.49.0",
"0.49.1",
"0.49.2",
"0.49.3",
"0.5.0",
"0.5.1",
"0.5.2",
"0.5.3",
"0.5.4",
"0.5.5",
"0.50.0",
"0.51.0",
"0.52.0",
"0.52.1",
"0.6.0",
"0.6.1",
"0.6.2",
"0.6.3",
"0.7.0",
"0.7.1",
"0.7.2",
"0.7.3",
"0.7.4",
"0.8.0",
"0.8.1",
"0.8.2",
"0.8.3",
"0.8.4",
"0.8.5",
"0.8.6",
"0.8.7",
"0.8.8",
"0.9.0",
"0.9.1",
"0.9.10",
"0.9.11",
"0.9.2",
"0.9.3",
"0.9.4",
"0.9.5",
"0.9.6",
"0.9.7",
"0.9.8",
"0.9.9",
"1.0.0",
"1.0.0rc1"
]
}
],
"aliases": [
"X41-2026-002",
"CVE-2026-48710",
"GHSA-86qp-5c8j-p5mr"
],
"details": "Starlette reconstructs the requested URL based on the HTTP Host request header and requested path, but does not perform any validation of the Host header value. This allows attackers to inject paths into the host part, prepending the actual path. However, routing in Starlette is based on the actual request path. This inconsistent interpretation of HTTP requests may lead to issues such as authentication bypass when the authentication depends on the reconstructed URL\u2019s path.",
"id": "PYSEC-2026-161",
"modified": "2026-05-22T13:11:38.659740Z",
"published": "2026-05-22T13:10:03Z",
"references": [
{
"type": "ARTICLE",
"url": "https://badhost.org"
},
{
"type": "ARTICLE",
"url": "https://www.secwest.net/starlette"
},
{
"type": "ARTICLE",
"url": "https://ostif.org/disclosing-the-badhost-vulnerability-in-starlette/"
},
{
"type": "DETECTION",
"url": "https://badhost.org"
},
{
"type": "EVIDENCE",
"url": "https://github.com/Kludex/starlette/security/advisories/GHSA-86qp-5c8j-p5mr"
},
{
"type": "ADVISORY",
"url": "https://github.com/Kludex/starlette/security/advisories/GHSA-86qp-5c8j-p5mr"
},
{
"type": "ADVISORY",
"url": "https://www.x41-dsec.de/lab/advisories/x41-2026-002-starlette/"
},
{
"type": "FIX",
"url": "https://github.com/Kludex/starlette/commit/764dab0dcfb9033d75442d7a359645c9f94648c6"
}
],
"summary": "BadHost: Missing Host header validation poisons request.url.path, bypassing path-based security checks"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.