vite allows server.fs.deny bypass via backslash on Windows
Published Oct 20, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
vite allows server.fs.deny bypass via backslash on Windows
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Files denied by server.fs.deny were sent if the URL ended with \ when the dev server is running on Windows.
Potential impact
Only apps that match the following conditions are affected: - explicitly exposes the Vite dev server to the network (using --host or server.host config option) - running the dev server on Windows
Technical context
server.fs.deny can contain patterns matching against files (by default it includes .env, .env., .{crt,pem} as such patterns). These patterns were able to bypass by using a back slash(\). The root cause is that fs.readFile('/foo.png/') loads /foo.png.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Oct 20, 2025 · Last refreshed Nov 3, 2026