CVE-2026-53571: Vite Server FS Deny Bypass Vulnerability on Windows

vite Updated 15 Jun 2026

Summary

15/06/2026
Yes i
High
8.2

CVE-2026-53571: vite: server.fs.deny bypass on Windows alternate paths. Affects vite across 3 version ranges.

< 6.4.3 >= 7.0.0, < 7.3.5 >= 8.0.0, < 8.0.16

Fixed in 6.4.3, 7.3.5 or 8.0.16, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Vite is a modern build tool that provides a fast and efficient development environment for web applications. It features hot module replacement, optimized builds, and a rich plugin ecosystem. However, Vite's development server has a vulnerability that allows sensitive files to be accessed under certain conditions, particularly on Windows systems.

Vulnerability Detail

The vulnerability arises from Vite's dev server failing to properly normalize NTFS Alternate Data Streams (ADS) paths before applying access checks for sensitive files specified in the server.fs.deny configuration. This oversight allows attackers to access sensitive files, such as .env or TLS certificates, via crafted requests that exploit Windows' handling of ADS. The impact is significant for applications that expose the Vite dev server to the network and have sensitive files in allowed directories, especially on NTFS volumes or when 8.3 short name generation is enabled.

How To Fix

Latest published version: 8.3.5 as of 22 Oct 2026

npm install vite@8.3.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 6.4.3 6.4.3
    npm install vite@6.4.3
  • >= 7.0.0, < 7.3.5 7.3.5
    npm install vite@7.3.5
  • >= 8.0.0, < 8.0.16 8.0.16
    npm install vite@8.0.16

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, avoid exposing the Vite dev server to the network by not using the '--host' option or by setting the server.host configuration to 'localhost'. Additionally, ensure that sensitive files are not placed in directories allowed by server.fs.allow.

Conclusion

CVE-2026-53571 is a critical vulnerability in the Vite development server that can lead to unauthorized access to sensitive files on Windows systems. Users are strongly advised to update to the latest patched versions of Vite to mitigate this risk. For immediate checks, Vulert provides a convenient way to monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for vite →

Share this vulnerability

FAQ

CVE-2026-53571 is a vulnerability in the Vite development server that allows unauthorized access to sensitive files on Windows systems.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which analyzes your package-lock.json for vulnerabilities.

Files such as .env, .env.*, and TLS certificates (e.g., *.crt, *.pem) are at risk of being accessed due to this vulnerability.

If you cannot update Vite immediately, consider restricting access to the Vite dev server and ensuring sensitive files are not in allowed directories.

The CVSS score of this vulnerability is 8.2, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for vite.

How To Fix

Latest published version: 8.3.5 as of 22 Oct 2026

npm install vite@8.3.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 6.4.3 6.4.3
    npm install vite@6.4.3
  • >= 7.0.0, < 7.3.5 7.3.5
    npm install vite@7.3.5
  • >= 8.0.0, < 8.0.16 8.0.16
    npm install vite@8.0.16

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback