Skip to main content
CVE-2026-48710VulnerabilityPublished Updated

Fastmcp: Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security

Affects fastmcpSource 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 3.3.1_1 now.

Data as of 30 Oct 2026, 10:15 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 3.3.1_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 29 Oct 2026.

What to do

Upgrade fastmcp to 3.3.1_1.

Affected software

ProductAffectedFixed in
Homebrewfastmcppkg:brew/fastmcpOther threatsAffected
  • >=2.12.3 <3.3.1_1
Fixed in
  • 3.3.1_1

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

AI-suggested

Upgrade to Starlette version 3.3.1_1 or later, which includes proper validation of the Host header per RFC 9112 and RFC 3986 and falls back to scope["server"] for malformed values. Alternatively, deploy an RFC-compliant reverse proxy (e.g., nginx, Apache, HAProxy, Caddy) in front of the ASGI server to reject malformed Host headers before they reach the application. These mitigations prevent the bypass of path-based security checks caused by malformed Host headers.

Description

A vulnerability in Fastmcp's Starlette framework allows an attacker to bypass path-based security checks by sending a malformed HTTP Host header. The Host header is not properly validated before reconstructing request.url, causing request.url.path to differ from the actual requested path. Applications relying on request.url.path for security decisions may be bypassed. The issue is fixed in version 3.3.1_1. Mitigation includes upgrading to the fixed version or deploying a reverse proxy that rejects malformed Host headers.

References

Community reviews

Loading reviews…