CVE-2025-32395: Vite has an `server.fs.deny` bypass with an invalid `request-target`
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
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-32395?
CVE-2025-32395 has a critical severity level due to the potential for exposing sensitive file contents.
How do I fix CVE-2025-32395?
To fix CVE-2025-32395, update Vite to version 6.2.6 or later, as it addresses this vulnerability.
What versions of Vite are affected by CVE-2025-32395?
Versions prior to 6.2.6, including 6.1.5, 6.0.15, 5.4.18, and 4.5.13, are affected by CVE-2025-32395.
What type of vulnerability is CVE-2025-32395?
CVE-2025-32395 is a path traversal vulnerability that allows the retrieval of arbitrary files from the server.
How can I mitigate the risk associated with CVE-2025-32395?
To mitigate the risk of CVE-2025-32395, ensure your development server is not exposing sensitive file paths and upgrade to a safe Vite version.