CVE-2026-39363: Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket

Published Apr 6, 2026
·
Updated

### Summary [`server.fs`](https://vite.dev/config/server-options#server-fs-strict) check was not enforced to the `fetchModule` method that is exposed in Vite dev server's WebSocket. ### Impact Only apps that match the following conditions are affected: - explicitly exposes the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) - WebSocket is not disabled by `server.ws: false` Arbitrary files on the server (development machine, CI environment, container, etc.) can be exposed. ### Details If it is possible to connect to the Vite dev server’s WebSocket **without an `Origin` header**, an attacker can invoke `fetchModule` via the custom WebSocket event `vite:invoke` and combine `file://...` with `?raw` (or `?inline`) to retrieve the contents of arbitrary files on the server as a JavaScript string (e.g., `export default "..."`). The access control enforced in the HTTP request path (such as `server.fs.allow`) is not applied to this WebSocket-based execution path. ### PoC 1. Start the dev server on the target Example (used during validation with this repository): ```bash pnpm -C playground/alias exec vite --host 0.0.0.0 --port 5173 ``` 2. Confirm that access is blocked via the HTTP path (example: arbitrary file) ```bash curl -i 'http://localhost:5173/@fs/etc/passwd?raw' ``` Result: `403 Restricted` (outside the allow list) <img width="3898" height="1014" alt="image" src="https://github.com/user-attachments/assets/f6593377-549c-45d7-b562-5c19833438af" /> 3. Confirm that the same file can be retrieved via the WebSocket path By connecting to the HMR WebSocket without an `Origin` header and sending a `vite:invoke` request that calls `fetchModule` with a `file://...` URL and `?raw`, the file contents are returned as a JavaScript module. <img width="1049" height="296" alt="image" src="https://github.com/user-attachments/assets/af969f7b-d34e-4af4-8adb-5e2b83b31972" /> <img width="1382" height="955" alt="image" src="https://github.com/user-attachments/assets/6a230d2e-197a-4c9c-b373-d0129756d5d7" />

Affected Software

7 affected componentsFixes available
npm/vite>=6.0.0<=6.4.1
6.4.2
npm/vite>=7.0.0<=7.3.1
7.3.2
npm/vite>=8.0.0<=8.0.4
8.0.5
vitejs Vite Node.js>=6.0.0<=6.4.1
vitejs Vite Node.js>=7.0.0<=7.3.1
vitejs Vite Node.js>=8.0.0<=8.0.4
Voidzero Vite\+ Node.js<=0.1.15

Event History

Apr 6, 2026
Advisory Published
via GitHub·06:03 PM
Data Sourced
via GitHub·06:03 PM
DescriptionWeaknessAffected Software
Apr 7, 2026
CVE Published
via MITRE·07:10 PM
Data Sourced
via MITRE·07:10 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
Affected Software
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-2026-39363?

CVE-2026-39363 has been rated as a high severity vulnerability due to the potential for arbitrary file read access.

2

How do I fix CVE-2026-39363?

To fix CVE-2026-39363, update Vite to version 6.4.2, 7.3.2, or 8.0.5 depending on your current version.

3

What versions of Vite are affected by CVE-2026-39363?

CVE-2026-39363 affects Vite versions from 6.0.0 to 6.4.1, 7.0.0 to 7.3.1, and 8.0.0 to 8.0.4.

4

What is the main impact of CVE-2026-39363?

The main impact of CVE-2026-39363 is the potential exposure of sensitive files through the Vite Dev Server WebSocket.

5

Is CVE-2026-39363 related to specific applications?

Yes, CVE-2026-39363 specifically impacts apps that use Vite's dev server with enabled WebSocket support.

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