fix(deps): update dependency vite to v6.2.7 [security] - autoclosed #4994

renovate · 2025-04-11T18:49:17Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`6.2.5` -> `6.2.7`

GitHub Vulnerability Alerts

CVE-2025-30208

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/@&#8203;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/@&#8203;fs/tmp/secret.txt?import&raw??"
export default "top secret content\n"
//# sourceMappingURL=data:application/json;base64,eyJ2...

CVE-2025-31125

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

CVE-2025-31486

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/@&#8203;fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&?raw'

CVE-2025-32395

Summary

The contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun.

Impact

Only apps with the following conditions are affected.

explicitly exposing the Vite dev server to the network (using --host or server.host config option)
running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun)

Details

HTTP 1.1 spec (RFC 9112) does not allow # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends to reject them with 400 or 301. The same can be said for HTTP 2 (ref1, ref2, ref3).

On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.fs.deny, allowing those kinds of requests to bypass the check.

On Deno, those requests are not rejected internally and is passed to the user land as well. But for those requests, the value of http.IncomingMessage.url did not contain #.

PoC

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

send request to read /etc/passwd

curl --request-target /@&#8203;fs/Users/doggy/Desktop/vite-project/#/../../../../../etc/passwd http://127.0.0.1:5173

CVE-2025-46565

Summary

The contents of files in the project root that are denied by a file matching pattern 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.
Only files that are under project root and are denied by a file matching pattern can be bypassed.

Examples of file matching patterns: .env, .env.*, *.{crt,pem}, **/.env
Examples of other patterns: **/.git/**, .git/**, .git/**/*

Details

server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns).
These patterns were able to bypass for files under root by using a combination of slash and dot (/.).

PoC

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173

Release Notes

vitejs/vite (vite)

`v6.2.7`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.2.6`

Compare Source

Please refer to CHANGELOG.md for details.

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

vercel · 2025-04-11T18:49:18Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
saltdesignsystem	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 1, 2025 0:40am

changeset-bot · 2025-04-11T18:49:21Z

⚠️ No Changeset found

Latest commit: 2d7bed7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel bot deployed to Preview April 11, 2025 18:53 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from f2936b1 to 969bee1 Compare April 14, 2025 10:19

vercel bot deployed to Preview April 14, 2025 10:27 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 969bee1 to 9f1b6ec Compare April 15, 2025 10:27

vercel bot deployed to Preview April 15, 2025 10:35 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 9f1b6ec to 480867d Compare April 15, 2025 15:48

vercel bot deployed to Preview April 15, 2025 15:56 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 480867d to 4f1a92c Compare April 17, 2025 08:06

vercel bot deployed to Preview April 17, 2025 08:15 View deployment

origami-z previously approved these changes Apr 17, 2025

View reviewed changes

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 4f1a92c to ae6cd0d Compare April 17, 2025 16:02

vercel bot deployed to Preview April 17, 2025 16:10 View deployment

renovate bot dismissed origami-z’s stale review via b98aa37 April 23, 2025 12:41

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from ae6cd0d to b98aa37 Compare April 23, 2025 12:41

vercel bot deployed to Preview April 23, 2025 12:50 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from b98aa37 to 87cf5ec Compare April 24, 2025 07:42

vercel bot deployed to Preview April 24, 2025 07:47 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 87cf5ec to d92860a Compare April 24, 2025 12:44

vercel bot deployed to Preview April 24, 2025 12:55 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from d92860a to 87bffb2 Compare April 24, 2025 15:10

vercel bot deployed to Preview April 24, 2025 15:18 View deployment

origami-z previously approved these changes Apr 25, 2025

View reviewed changes

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 87bffb2 to e4d6826 Compare April 25, 2025 07:43

vercel bot deployed to Preview April 25, 2025 07:53 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from e4d6826 to adc4047 Compare April 25, 2025 14:41

vercel bot deployed to Preview April 25, 2025 14:58 View deployment

renovate bot dismissed origami-z’s stale review via 07dcd72 April 25, 2025 18:21

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from adc4047 to 07dcd72 Compare April 25, 2025 18:21

vercel bot deployed to Preview April 25, 2025 18:34 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 07dcd72 to 2be56e1 Compare April 28, 2025 12:38

vercel bot deployed to Preview April 28, 2025 12:49 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 2be56e1 to ae539b7 Compare April 30, 2025 09:06

renovate bot changed the title ~~fix(deps): update dependency vite to v6.2.6 [security]~~ Update dependency vite to v6.2.6 [SECURITY] Apr 30, 2025

vercel bot deployed to Preview April 30, 2025 09:14 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from ae539b7 to bfcf325 Compare April 30, 2025 12:43

vercel bot deployed to Preview April 30, 2025 12:55 View deployment

renovate bot changed the title ~~Update dependency vite to v6.2.6 [SECURITY]~~ Update dependency vite to v6.2.7 [SECURITY] Apr 30, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from bfcf325 to f4b0bf2 Compare May 1, 2025 09:01

vercel bot deployed to Preview May 1, 2025 09:18 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from f4b0bf2 to f2426f0 Compare May 1, 2025 09:24

renovate bot changed the title ~~Update dependency vite to v6.2.7 [SECURITY]~~ fix(deps): update dependency vite to v6.2.7 [security] May 1, 2025

vercel bot deployed to Preview May 1, 2025 10:01 View deployment

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from f2426f0 to 6c360b5 Compare May 1, 2025 10:09

vercel bot deployed to Preview May 1, 2025 10:21 View deployment

fix(deps): update dependency vite to v6.2.7 [security]

2d7bed7

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 6c360b5 to 2d7bed7 Compare May 1, 2025 12:31

vercel bot deployed to Preview May 1, 2025 12:40 View deployment

Fercas123 approved these changes May 1, 2025

View reviewed changes

renovate bot changed the title ~~fix(deps): update dependency vite to v6.2.7 [security]~~ fix(deps): update dependency vite to v6.2.7 [security] - autoclosed May 1, 2025

renovate bot closed this May 1, 2025

renovate bot deleted the renovate/npm-vite-vulnerability branch May 1, 2025 13:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency vite to v6.2.7 [security] - autoclosed #4994

fix(deps): update dependency vite to v6.2.7 [security] - autoclosed #4994

renovate bot commented Apr 11, 2025 •

edited

Loading

vercel bot commented Apr 11, 2025 •

edited

Loading

changeset-bot bot commented Apr 11, 2025 •

edited

Loading

fix(deps): update dependency vite to v6.2.7 [security] - autoclosed #4994

fix(deps): update dependency vite to v6.2.7 [security] - autoclosed #4994

Conversation

renovate bot commented Apr 11, 2025 • edited Loading

GitHub Vulnerability Alerts

CVE-2025-30208

Summary

Impact

Details

PoC

CVE-2025-31125

Summary

Impact

Details

PoC

CVE-2025-31486

Summary

Impact

Details

.svg

relative paths

PoC

CVE-2025-32395

Summary

Impact

Details

PoC

CVE-2025-46565

Summary

Impact

Details

PoC

Release Notes

v6.2.7

v6.2.6

Configuration

vercel bot commented Apr 11, 2025 • edited Loading

changeset-bot bot commented Apr 11, 2025 • edited Loading

⚠️ No Changeset found

renovate bot commented Apr 11, 2025 •

edited

Loading

`.svg`

`v6.2.7`

`v6.2.6`

vercel bot commented Apr 11, 2025 •

edited

Loading

changeset-bot bot commented Apr 11, 2025 •

edited

Loading