FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2026-48710

Kludex · Starlette · Kludex Starlette HTTP Request/Response Smuggling Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 1% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-09-02 · exploited in the wild for 66 days

How a test catches it

Test
Send a request where Content-Length and Transfer-Encoding disagree, then one carrying an absolute-form request target, and count how many requests the backend sees.
Passes when
The front end rejects the ambiguity. Two backend responses to one client request is the finding, and counting the backend's responses is the only way to see it - both connections return 200.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 6.5 MEDIUM. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionnonecan be triggered with nobody interacting with the page or request
Base vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
WeaknessCWE-444

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.7029, which places it in the top 1% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.7029
Percentile0.994 — top 1%

Time

Added to KEV2026-09-02
Days exploited66
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP `Host` request header was not validated before being used to reconstruct `request.url`. Because the routing algorithm relies on the raw HTTP path while `request.url` is rebuilt from the `Host` header, a malformed header could make `request.url.path` differ from the path that was actually requested. Middleware and endpoints that apply security restrictions based on `request.url` (rather than the raw `scope` path) could therefore be bypassed. Users should upgrade to a version greater than or equal to version 1.0.1, which validates the `Host` header against the grammar of RFC 9112 §3.2 / RFC 3986 §3.2.2 when constructing `request.url` and falls back to `scope["server"]` for malformed values.

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service