CVE-2025-32395

Vite has an `server.fs.deny` bypass with an invalid `request-target`

MEDIUM
6
CVSS Score
Published: April 10, 2025 at 01:25 PM UTC
Updated: June 17, 2026 at 09:11 AM UTC
1 product affected across 1 vendorVite

Using vite by vitejs?

Get instant alerts when new vulnerabilities affect vite - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6
Exploit prediction
EPSS 2%
SSVC
PoC

Description

Vite is a frontend tooling framework for javascript. Prior to 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13, the contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun. HTTP 1.1 spec (RFC 9112) does not allow # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends to reject them with 400 or 301. The same can be said for HTTP 2. On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.fs.deny, allowing those kinds of requests to bypass the check. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) and running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun) are affected. This vulnerability is fixed in 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.5.13v < 5.4.18v < 6.0.15v < 6.1.5v < 6.2.6
Affected range stops below 4.5.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card