All reports
Medium

Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

Affected versions

Affected versions
>= 6.1.0, < 6.1.3
Fixed version
6.1.3
Affected versions
< 4.5.11
Fixed version
4.5.11
Affected versions
>= 6.2.0, < 6.2.4
Fixed version
6.2.4
Affected versions
>= 5.0.0, < 5.4.16
Fixed version
5.4.16
Affected versions
>= 6.0.0, < 6.0.13
Fixed version
6.0.13
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-31125

Exploitation in the wild has been reported · CISA KEV

Date added: 2026-01-22

Probability of exploitation in the next 30 days: 74.94%

FIRST EPSS · 2026-11-21

Description

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
  • base64 encoded content of non-allowed files is exposed using ?inline&import (originally reported as ?import&?inline=1.wasm?init)

  • content of non-allowed files is exposed using ?raw?import

/@fs/ isn't needed to reproduce the issue for files inside the project root.

PoC

Original report (check details above for simplified cases):

The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice

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

Example full URL http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init

Links

Credits

  • Iuhsssss