# vite: \`server.fs.deny\` bypass on Windows alternate paths

Advisory record · `GHSA-fx2h-pf6j-xcff`

- **Identifiers:** `GHSA-fx2h-pf6j-xcff` · `CVE-2026-53571`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 15 Jun 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Jun 2026, 17:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vite` (npm): affected `>=8.0.0, <8.0.16 || >=7.0.0, <7.3.5 || <6.4.3`; fixed in `8.0.16`, `7.3.5`, `6.4.3`
- `vite-plus` (npm): affected `<0.1.24`; fixed in `0.1.24`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vite's dev server can return files that \`server.fs.deny\` is meant to block on Windows, affecting the vite package before 6.4.3, 7.0.0 up to 7.3.5, and 8.0.0 up to 8.0.16, and the vite-plus package before 0.1.24. An attacker who can reach a dev server that was exposed to the network with \`--host\` or \`server.host\`, and where a sensitive file such as a \`.env\` or certificate sits in an allowed directory on an NTFS volume (or a volume with 8.3 short names enabled), could read that file's contents. Upgrade vite to 6.4.3, 7.3.5, or 8.0.16, or vite-plus to 0.1.24.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0058, the 48th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 Jun 2026, 13:32 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/vitejs/vite/security/advisories/GHSA-fx2h-pf6j-xcff)
- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fx2h-pf6j-xcff)

## Sources

- [GitHub Advisory Database: GHSA-fx2h-pf6j-xcff](https://github.com/advisories/GHSA-fx2h-pf6j-xcff)
- [OSV: GHSA-fx2h-pf6j-xcff](https://osv.dev/vulnerability/GHSA-fx2h-pf6j-xcff)
- <https://github.com/vitejs/vite/security/advisories/GHSA-fx2h-pf6j-xcff>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-53571>
- <https://github.com/vitejs/vite>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fx2h-pf6j-xcff>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fx2h-pf6j-xcff/>. Everything for agents: <https://agentprime.io/llms.txt>.
