NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-53571: vite: `server.fs.deny` bypass on Windows alternate paths

mediumCVSS 4.0 6.9GHSA-fx2h-pf6j-xcff

Summary The contents of files that are specified by server.fs.deny can be returned to the browser on Windows. 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) - the sensitive file exists in the allowed directories specified by server.fs.allow - either of: - the sensitive file exists in an NTFS volume…

Published Jun 15, 2026 · Updated Oct 27, 2026

Affected packages

vite

Ecosystem
npm
Affected
>= 8.0.0, <= 8.0.15
Fixed in
8.0.16
Check
npm ls vite

vite

Ecosystem
npm
Affected
>= 7.0.0, <= 7.3.4
Fixed in
7.3.5
Check
npm ls vite

vite

Ecosystem
npm
Affected
<= 6.4.2
Fixed in
6.4.3
Check
npm ls vite

vite-plus

Ecosystem
npm
Affected
<= 0.1.23
Fixed in
0.1.24
Check
npm ls vite-plus

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

The contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.

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)
  • the sensitive file exists in the allowed directories specified by `server.fs.allow`
  • either of:
  • the sensitive file exists in an NTFS volume
  • the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)

Details

Vite’s dev server denies direct access to sensitive files through server.fs.deny, including entries such as .env, .env.*, and *.{crt,pem}. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied. Because of this, requests such as /.env::$DATA?raw are treated as allowed paths, while Windows resolves them to the original file's default data stream.

Similar to that, Windows allows accessing a file using a different name with the 8.3 short name compatibility feature. Vite did not reject accessing files via them.

PoC

$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev

Access via browser at http://localhost:5173/.env::$DATA?raw

Example expected result:

  • /.env::$DATA?raw returns the contents of .env
  • /tls.pem::$DATA?raw returns the contents of tls.pem

Credited to TazmiDev, 332QAQ, ArnaudBarre.

References

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 entries