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

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

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** CLEANSTART-2026-TV89664, CLSA-2026-1784423356, CLSA-2026-1787839491, CLSA-2026-1788814439, CLSA-2026-1792225954, GHSA-fx2h-pf6j-xcff, MINI-2f7m-r4qj-fmg2, MINI-3fvf-x4rf-q2pp, MINI-c448-ph76-h58m, MINI-gv8w-4q6h-m8rm, MINI-h53v-cvgc-4ffm, MINI-j3qf-xxjh-q5w8, MINI-j6gp-rjgf-3cmm, MINI-mcgp-fhc6-qj88, MINI-wxj2-w86m-7834, ROOT-APP-NPM-CVE-2026-53571

## 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 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vite` | npm | All versions | 6.4.3 |
| `vite` | npm | All versions | 6.4.3 |
| `vite` | npm | From 7.0.0 | 7.3.5 |
| `vite` | npm | From 7.0.0 | 7.3.5 |
| `vite` | npm | From 8.0.0 | 8.0.16 |
| `vite` | npm | From 8.0.0 | 8.0.16 |
| `vite-plus` | npm | All versions | 0.1.24 |
| `vite-plus` | npm | All versions | 0.1.24 |

Products: 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.

## 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:

- CVE-2026-53571 `server.fs.deny` bypass on Windows alternate paths PoC. (github_poc): https://github.com/TazmiDev/CVE-2026-53571

## Other vulnerabilities in vitejs vite

- [CVE-2025-31125](https://insights.sbomify.com/CVE-2025-31125/): Vite Vitejs Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2026-39363](https://insights.sbomify.com/CVE-2026-39363/): Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket (high 8.2)
- [CVE-2026-39364](https://insights.sbomify.com/CVE-2026-39364/): Vite has a `server.fs.deny` bypass with queries (high 8.2)
- [CVE-2024-23331](https://insights.sbomify.com/CVE-2024-23331/): Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem (high 7.5)
- [CVE-2023-34092](https://insights.sbomify.com/CVE-2023-34092/): Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53571 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53571 exists.

Affected packages and fixed versions:
- vite (npm): affected all versions; fixed in 6.4.3
- vite (npm): affected all versions; fixed in 6.4.3
- vite (npm): affected from 7.0.0; fixed in 7.3.5
- vite (npm): affected from 7.0.0; fixed in 7.3.5
- vite (npm): affected from 8.0.0; fixed in 8.0.16
- vite (npm): affected from 8.0.0; fixed in 8.0.16
- vite-plus (npm): affected all versions; fixed in 0.1.24
- vite-plus (npm): affected all versions; fixed in 0.1.24

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53571/ (Markdown: https://insights.sbomify.com/CVE-2026-53571/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53571
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53571
- OSV: https://osv.dev/vulnerability/CVE-2026-53571

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53571/
Summaries are generated and may contain mistakes; the official description above is the record.