CVE-2026-53571

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

HIGH
7.5
CVSS Score
Published: June 22, 2026 at 04:10 PM UTC
Updated: October 25, 2026 at 11:10 PM UTC
2 products affected across 2 vendorsViteVite+· also runs on 1 platform

Using vite by vitejs?

Get instant alerts when new vulnerabilities affect vite - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versionsv < 6.4.37.0.0 ≤ v < 7.3.58.0.0 ≤ v < 8.0.16
Affected range stops below 6.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.0.16, so it looks safe — our inference, not a vendor statement
microsoft-windows (environment)
All versionsv < 0.1.24
Affected range stops below 0.1.24, so it looks safe — our inference, not a vendor statement
microsoft-windows (environment)

Runs on — not affected

The affected product only carries this flaw when running on these platforms. The platforms themselves are not vulnerable.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/vitejs/vite/security/advisories/GHSA-fx2h-pf6j-xcff

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-22CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card