CVE-2025-31125: Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query
Summary The contents of arbitrary files can be returned to the browser. Impact Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected. Details - base64 encoded content of non-allowed files is exposed using ?inline&import (originally reported as ?import&?inline=1.wasm?init) - content of non-allowed files is exposed using ?raw?import /@fs/ isn't needed…
Published Mar 31, 2025 · Updated Jan 22, 2026
Affected packages
vite
- Ecosystem
- npm
- Affected
- >= 6.2.0, < 6.2.4
- Fixed in
- 6.2.4
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 6.1.0, < 6.1.3
- Fixed in
- 6.1.3
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 6.0.0, < 6.0.13
- Fixed in
- 6.0.13
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 5.0.0, < 5.4.16
- Fixed in
- 5.4.16
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- < 4.5.11
- Fixed in
- 4.5.11
- Check
npm ls vite
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The contents of arbitrary files can be returned to the browser.
Impact
Only apps explicitly exposing the Vite dev server to the network (using --host or `server.host` config option) are affected.
Details
- base64 encoded content of non-allowed files is exposed using
?inline&import(originally reported as?import&?inline=1.wasm?init) - content of non-allowed files is exposed using
?raw?import
/@fs/ isn't needed to reproduce the issue for files inside the project root.
PoC
Original report (check details above for simplified cases):
The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice
$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run devExample full URL http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init
Credited to Iuhsssss.
References
- https://github.com/vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8
- https://github.com/vitejs/vite/commit/59673137c45ac2bcfad1170d954347c1a17ab949
- https://nvd.nist.gov/vuln/detail/CVE-2025-31125
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-31125
- https://github.com/advisories/GHSA-4r4m-qw57-chr8
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118662
Vite: `server.fs.deny` bypassed with queries
medium6.9Oct 29, 2026CVE-2026-112945
Vite: Cross origin script execution through Vite custom middleware
low2.1Oct 21, 2026CVE-2026-112946
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
medium6.3Oct 21, 2026CVE-2026-112947
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
medium6.3Oct 21, 2026CVE-2026-112942
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
high7.5Oct 20, 2026CVE-2026-112943
launch-editor: escapeCmdArgs() omits % escaping on Windows
medium6.3Oct 20, 2026
