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

High 8.2 Published Updated

Attackers can bypass file access restrictions on Windows to read sensitive files like .env via NTFS alternate data streams or short names.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-53571?

CVE-2026-53571 is a high-severity path traversal vulnerability in vitejs vite, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Vite is a frontend tooling framework for JavaScript. Prior to 8.0.16, 7.3.5, and 6.4.3, the contents of files that are specified by server.fs.deny can be returned to the browser on Windows. 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. This vulnerability is fixed in 8.0.16, 7.3.5, and 6.4.3.

Weakness: CWE-22, CWE-200

Which versions are affected by CVE-2026-53571?

8 open source packages ship an affected version, including vite and vite-plus. It affects 2 products.

PackageAffectedFixed in
vite npmAll versions6.4.3
vite npmAll versions6.4.3
vite npmFrom 7.0.07.3.5
vite npmFrom 7.0.07.3.5
vite npmFrom 8.0.08.0.16
vite npmFrom 8.0.08.0.16
2 more packages
vite-plus npmAll versions0.1.24
vite-plus npmAll versions0.1.24

Products include Vitejs Vite, Voidzero Vite\+.

How do I fix CVE-2026-53571?

Upgrade vite to a fixed version for your release line: 6.4.3, 7.3.5 or 8.0.16.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-53571 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53571 exists.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as CLEANSTART-2026-TV89664, CLSA-2026-1784423356, CLSA-2026-1787839491, CLSA-2026-1788814439, CLSA-2026-1792225954, GHSA-fx2h-pf6j-xcff and 10 more.

Is CVE-2026-53571 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free