HighGHSA-fx2h-pf6j-xcffCVE-2026-53571

vite: `server.fs.deny` bypass on Windows alternate paths

Published 15 Jun 2026 · Updated 10 Sept 2026

Affected packages

vitenpm

Affected: >=8.0.0 <8.0.16
Fixed in: 8.0.16

Update to the fixed version for your release line, for example:npm install vite@8.0.16

vitenpm

Affected: >=7.0.0 <7.3.5
Fixed in: 7.3.5

Update to the fixed version for your release line, for example:npm install vite@7.3.5

vitenpm

Affected: <6.4.3
Fixed in: 6.4.3

Update to the fixed version for your release line, for example:npm install vite@6.4.3

vite-plusnpm

Affected: <0.1.24
Fixed in: 0.1.24

Update to the fixed version for your release line, for example:npm install vite-plus@0.1.24

Details

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 <img width="388" height="129" alt="deecc1315123883cfd0f9c26a002845a" src="https://github.com/user-attachments/assets/895c6012-4e2e-4a35-babb-69bbf3ee7170" />

Example expected result:

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

Is GHSA-fx2h-pf6j-xcff in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vite, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.