Quick answers
- Is CVE-2026-53571 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53571 being exploited in the wild.
- How severe is CVE-2026-53571?
- High severity, with a CVSS score of 3.1, published 22 June 2026.
- Which products and versions are affected?
- vite-plus (npm) <= 0.1.23, SEMVER:introduced=0,fixed=0.1.24; Vite >= 8.0.0, <= 8.0.15; >= 7.0.0, <= 7.3.4; <= 6.4.2.
- Is there a fix for CVE-2026-53571?
- Yes. vite-plus (npm): upgrade to 0.1.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53571 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53571?
- Check whether you run vite-plus (npm) or Vite at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vite-plus (npm): upgrade to 0.1.24 or later
npm install vite-plus@0.1.24
Technical details
A path traversal and information disclosure vulnerability exists in the Vite development server when running on Windows. The 'server.fs.deny' configuration, which is intended to block access to sensitive files like .env or .crt, fails to account for NTFS Alternate Data Streams (ADS) and 8.3 short file names. An attacker can bypass these checks by requesting files using suffixes like '::$DATA' or by using shortened Windows file aliases. This allows a remote attacker to read the contents of restricted files if the dev server is configured to listen on a network interface. The issue is fixed in versions 8.0.16, 7.3.5, and 6.4.3.
Affected products
- vitejs Vite >= 8.0.0, < 8.0.16; >= 7.0.0, < 7.3.5; < 6.4.3
- vitejs vite-plus <= 0.1.23
Identifiers
- CVE-2026-53571
- GHSA-fx2h-pf6j-xcff
Timeline
- 2026-06-01: advisory: GitHub Security Advisory published
- 2026-06-22: disclosed: CVE published to NVD