MediumGHSA-356w-63v5-8wf4CVE-2025-32395

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

Published 11 Apr 2025 · Updated 10 Sept 2026

Affected packages

vitenpm

Affected: >=6.2.0 <6.2.6
Fixed in: 6.2.6

Update to the fixed version for your release line, for example:npm install vite@6.2.6

vitenpm

Affected: >=6.1.0 <6.1.5
Fixed in: 6.1.5

Update to the fixed version for your release line, for example:npm install vite@6.1.5

vitenpm

Affected: >=6.0.0 <6.0.15
Fixed in: 6.0.15

Update to the fixed version for your release line, for example:npm install vite@6.0.15

vitenpm

Affected: >=5.0.0 <5.4.18
Fixed in: 5.4.18

Update to the fixed version for your release line, for example:npm install vite@5.4.18

vitenpm

Affected: <4.5.13
Fixed in: 4.5.13

Update to the fixed version for your release line, for example:npm install vite@4.5.13

Details

Summary

The contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun.

Impact

Only apps with the following conditions are affected.

explicitly exposing the Vite dev server to the network (using --host or server.host config option)
running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun)

Details

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 (ref1, ref2, ref3).

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.

On Deno, those requests are not rejected internally and is passed to the user land as well. But for those requests, the value of http.IncomingMessage.url did not contain #.

PoC

npm create vite@latest
cd vite-project/
npm install
npm run dev

send request to read /etc/passwd

curl --request-target /@fs/Users/doggy/Desktop/vite-project/#/../../../../../etc/passwd http://127.0.0.1:5173

Is GHSA-356w-63v5-8wf4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vite, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.