CVE-2024-31207: Vite's `server.fs.deny` did not deny requests for patterns with directories.
Summary Vite dev server option server.fs.deny did not deny requests for patterns with directories. An example of such a pattern is /foo//. Impact Only apps setting a custom server.fs.deny that includes a pattern with directories, and explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Published Apr 3, 2024 · Updated Apr 4, 2024
Affected packages
vite
- Ecosystem
- npm
- Affected
- >= 2.7.0, <= 2.9.17
- Fixed in
- 2.9.18
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 3.0.0, <= 3.2.8
- Fixed in
- 3.2.10
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 4.0.0, <= 4.5.2
- Fixed in
- 4.5.3
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 5.0.0, <= 5.0.12
- Fixed in
- 5.0.13
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 5.1.0, <= 5.1.6
- Fixed in
- 5.1.7
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 5.2.0, <= 5.2.5
- Fixed in
- 5.2.6
- Check
npm ls vite
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Vite dev server option server.fs.deny did not deny requests for patterns with directories. An example of such a pattern is /foo/**/*.
Impact
Only apps setting a custom server.fs.deny that includes a pattern with directories, and explicitly exposing the Vite dev server to the network (using --host or `server.host` config option) are affected.
Patches
Fixed in [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Details
server.fs.deny uses picomatch with the config of { matchBase: true }. matchBase only matches the basename of the file, not the path due to a bug (https://github.com/micromatch/picomatch/issues/89). The vite config docs read like you should be able to set fs.deny to glob with picomatch. Vite also does not set { dot: true } and that causes dotfiles not to be denied unless they are explicitly defined.
Reproduction
Set fs.deny to ['**/.git/**'] and then curl for /.git/config.
- with
matchBase: true, you can get any file under.git/(config, HEAD, etc). - with
matchBase: false, you cannot get any file under.git/(config, HEAD, etc).
Credited to jtmcdole.
References
- https://github.com/vitejs/vite/security/advisories/GHSA-8jhw-289h-jh2g
- https://github.com/vitejs/vite/commit/011bbca350e447d1b499d242804ce62738c12bc0
- https://github.com/vitejs/vite/commit/5a056dd2fc80dbafed033062fe6aaf4717309f48
- https://github.com/vitejs/vite/commit/89c7c645f09d16a38f146ef4a1528f218e844d67
- https://github.com/vitejs/vite/commit/96a7f3a41ef2f9351c46f3ab12489bb4efa03cc9
- https://github.com/vitejs/vite/commit/ba5269cca81de3f5fbb0f49d58a1c55688043258
- https://github.com/vitejs/vite/commit/d2db33f7d4b96750b35370c70dd2c35ec3b9b649
- https://nvd.nist.gov/vuln/detail/CVE-2024-31207
- https://github.com/advisories/GHSA-8jhw-289h-jh2g
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118662
Vite: `server.fs.deny` bypassed with queries
medium6.9Oct 29, 2026CVE-2026-112945
Vite: Cross origin script execution through Vite custom middleware
low2.1Oct 21, 2026CVE-2026-112946
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
medium6.3Oct 21, 2026CVE-2026-112947
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
medium6.3Oct 21, 2026CVE-2026-112942
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
high7.5Oct 20, 2026CVE-2026-112943
launch-editor: escapeCmdArgs() omits % escaping on Windows
medium6.3Oct 20, 2026
