Skip to main content
CVE-2026-48710VulnerabilityPublished Updated

Snyk agent scan: Starlette has missing Host header validation that poisons request.url.path, bypassing path-based

Affects Kludex snyk-agent-scanSource GCVE Database

0
Compare
Authoritative record:CVE-2026-48710· Medium 6.5

Exploited in the wild · KEV due 16 Sep 2026 · public detection template (Nuclei) : upgrade to 0.5.4_1 now.

Data as of 1 Nov 2026, 01:51 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
Patch
Available – fixed in 0.5.4_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 26 May 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 99 days after disclosure

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 4 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 24 minutes after disclosure

  4. , 99 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 113 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade Kludex snyk-agent-scan to 0.5.4_1.

Affected software

ProductAffectedFixed in
Homebrewsnyk-agent-scanpkg:brew/snyk-agent-scanOther threatsAffected
  • >=0.4.3 <0.5.4_1
Fixed in
  • 0.5.4_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Starlette versions from 0.4.3 up to but not including 0.5.4_1 have a vulnerability where the HTTP Host header is not validated before reconstructing request.url. This allows an attacker to craft a malformed Host header that causes request.url.path to differ from the actual requested path, potentially bypassing path-based security checks that rely on request.url.path. The issue is fixed in version 0.5.4_1 by validating the Host header against RFC 9112 and RFC 3986 grammar and falling back to a safe value if malformed.

References

Community reviews

Loading reviews…