CVE-2025-32395: Vite has an `server.fs.deny` bypass with an invalid `request-target`

Published Apr 10, 2025
·
Updated

### 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](https://vitejs.dev/config/server-options.html#server-host)) - 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`](https://datatracker.ietf.org/doc/html/rfc9112#section-3.2). 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](https://datatracker.ietf.org/doc/html/rfc9112#section-3.2-4). The same can be said for HTTP 2 ([ref1](https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1-2.4.1), [ref2](https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1-3), [ref3](https://datatracker.ietf.org/doc/html/rfc9113#section-8.1.1-3)). 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`](https://nodejs.org/docs/latest-v22.x/api/http.html#messageurl) 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 ```

Affected Software

7 affected componentsFixes available
Vite Vite<6.2.6
Vite Vite
npm/vite<4.5.13
4.5.13
npm/vite>=5.0.0<5.4.18
5.4.18
npm/vite>=6.0.0<6.0.15
6.0.15
npm/vite>=6.1.0<6.1.5
6.1.5
npm/vite>=6.2.0<6.2.6
6.2.6

Event History

Apr 10, 2025
CVE Published
via MITRE·01:25 PM
Data Sourced
via MITRE·01:25 PM
DescriptionWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
Apr 11, 2025
Advisory Published
via GitHub·02:06 PM
Dec 11, 57260
Event
via FIRST·03:56 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203