NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 32/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: vitejs vite 8.0.16.

Low priority for now. Upgrade to vitejs vite 8.0.16 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.2 · v4.0—Proof of concept Fix available

Published: Jun 22, 2026
Updated: Oct 25, 2026
EPSS: 0.5% · 47th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 8.2; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
vitejs	vite	cpe:2.3:a:vitejs:vite
voidzero	vite+	cpe:2.3:a:voidzero:vite+
microsoft	windows	cpe:2.3:o:microsoft:windows

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

vitejs vitebefore 6.4.3
vitejs vite7.0.0 and later · before 7.3.5
vitejs vite8.0.0 and later · before 8.0.16
voidzero vite+before 0.1.24

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

vitejs vite
- >= 8.0.0, < 8.0.16, >= 7.0.0, < 7.3.5, < 6.4.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	vite	from 7.0.0 · before 7.3.5	7.3.5
npm	vite	from 8.0.0 · before 8.0.16	8.0.16
npm	vite	before 6.4.3	6.4.3
npm	vite-plus	before 0.1.24	0.1.24

Same product

vitejs: all records

Other highest-scoring records for the same primary product.

CVE-2025-31125Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryKEV
82Now
CVE-2025-30208Vite bypasses server.fs.deny when using `?raw??`
52Plan
CVE-2026-39364Vite has a `server.fs.deny` bypass with queries
33Monitor

Published before and after this one in the same product

← EarlierCVE-2026-39363Apr 7, 2026 · Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket
33Monitor
← EarlierCVE-2026-39365Apr 7, 2026 · Vite has a Path Traversal in Optimized Deps `.map` Handling
25Monitor
Later →CVE-2026-112945Oct 20, 2026 · Vite: Cross origin script execution through Vite custom middleware
8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
vitejs vite	8.0.16 · description	Vendor (CNA)
npm:vite	6.4.3	Package registry (OSV)
npm:vite	7.3.5	Package registry (OSV)
npm:vite	8.0.16	Package registry (OSV)
npm:vite-plus	0.1.24	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:1	2026-07-09

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedJun 22, 2026
First PoCJul 9, 2026+16 d
TodayOct 31, 2026+131 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-3936576 days apartVite has a Path Traversal in Optimized Deps `.map` Handling
25Monitor
CVE-2026-112946120 days apartVite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
25Monitor
CVE-2026-112947120 days apartVite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
25Monitor
CVE-2025-62522245 days apartvite allows server.fs.deny bypass via backslash on Windows
24Monitor
CVE-2025-46565417 days apartVite's server.fs.deny bypassed with /. for files under project root
24Monitor
CVE-2025-58751287 days apartVite middleware may serve files starting with the same name with the public directory
9Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: GitHub_M

CVE.org (CNA)Jun 22, 2026, 6:07 PM UTC
CISA ADPJun 22, 2026, 6:07 PM UTC
NVDOct 25, 2026, 11:10 PM UTC
FIRST EPSSOct 30, 2026, 12:00 AM UTC
OSV / GHSAOct 31, 2026, 3:18 AM UTC
PoC-in-GitHubOct 31, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.