Packages / vite / Security

ModerateVulnerabilityGHSA-356w-63v5-8wf4CVE-2025-32395Published 11 Apr 2025

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

Affected releases · vite

  • 6.x6.0.0 – 6.2.5Fixed in 6.2.6
  • 5.x5.0.0 – 5.4.17Fixed in 5.4.18
  • 4.x4.0.0 – 4.5.12Fixed in 4.5.13
  • 3.x and older0.1.0 – 3.2.11No fix, no longer updated

On 6.x, the newest line:

npm install vite@6.2.6
8.x

  1. Not affected

    8.0.0 – 8.3.5

    34 releases, latest

6.x

  1. Affected

    6.0.0 – 6.0.14

    15 releases

  2. Fixed

    6.0.15

    1 release

  3. Affected

    6.1.0 – 6.1.4

    5 releases

  4. Fixed

    6.1.5 – 6.1.6

    2 releases

  5. Affected

    6.2.0 – 6.2.5

    6 releases

  6. Fixed

    6.2.6 – 6.4.5

    16 releases

5.x

  1. Affected

    5.0.0 – 5.4.17

    63 releases

  2. Fixed

    5.4.18 – 5.4.21

    4 releases

4.x

  1. Affected

    4.0.0 – 4.5.12

    51 releases

  2. Fixed

    4.5.13 – 4.5.14

    2 releases

3.x

  1. Affected

    3.0.0 – 3.2.11

    30 releases

2.x

  1. Affected

    2.0.0 – 2.9.18

    97 releases

0.x

  1. Affected

    0.1.0 – 0.20.10

    78 releases

440 stable releases of vite, oldest to newest, one row per major.

Is your project affected?

Paste your package.json, or type the range you declare for vite. It is read in your browser and sent nowhere.

What happens

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