Starlette is a lightweight ASGI framework/toolkit. Prior to 1.3.0, the HTTP request path is not validated before being used to reconstruct request.url. Because request.url is rebuilt by concatenating {scheme}://{host}{path} and re-parsing the result, a path that does not begin with / (for example @google.com) moves the authority boundary during re-parsing, so request.url.hostname and request.url.netloc become attacker-controlled. Code that reads request.url.hostname (rather than the Host header or scope) can therefore be misled into trusting an attacker-supplied host. This vulnerability is fixed in 1.3.0.
CVE-2026-54282
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 8.5%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026Unvalidated request path concatenated into authority poisons request.url.hostname · Advisory · Kludex/starlette · GitHub
https://github.com/Kludex/starlette/security/advisories/GHSA-jp82-jpqv-5vv3Vendor Advisories for CVE-2026-54282(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| starlette | 0.1.0 ... 1.2.1 (195 versions) | 1.3.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:15 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 14:57 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 14:29 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 14:12 UTCEG score recompute
- 2026-07-02 13:38 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 13:20 UTCEG score recompute
- 2026-06-30 12:57 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 10:36 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:17 UTCEG score recompute▲ 1.60
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:41 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
Show 8 moreShow fewer
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 07:04 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 03:42 UTCEG score recompute
- 2026-06-18 23:55 UTCEG score recompute
- 2026-06-15 20:45 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-54282?
When was CVE-2026-54282 disclosed?
Is CVE-2026-54282 actively exploited?
What is the CVSS score of CVE-2026-54282?
How do I remediate CVE-2026-54282?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54282
Is Your Infrastructure Affected by CVE-2026-54282?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.