chore(deps): update dependency vite to v6.2.6 [security] #2526

renovate · 2025-03-25T16:45:46Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`6.2.2` -> `6.2.6`

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

Release Notes

vitejs/vite (vite)

`v6.2.6`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.2.5`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.2.4`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.2.3`

Compare Source

Please refer to CHANGELOG.md for details.

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

changeset-bot · 2025-03-25T16:45:50Z

⚠️ No Changeset found

Latest commit: bb7a601

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

codecov · 2025-03-25T16:49:54Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.76%. Comparing base (1f922c5) to head (bb7a601).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2526   +/-   ##
=======================================
  Coverage   78.76%   78.76%           
=======================================
  Files          26       26           
  Lines         871      871           
  Branches      112      112           
=======================================
  Hits          686      686           
  Misses        172      172           
  Partials       13       13

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

renovate bot added the UPDATE-PATCH label Mar 25, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 3 times, most recently from b90b8bf to b3a4c8f Compare March 31, 2025 18:25

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.3 [security]~~ chore(deps): update dependency vite to v6.2.4 [security] Mar 31, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from b3a4c8f to f3d8262 Compare April 1, 2025 08:29

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

renovate bot closed this Apr 1, 2025

renovate bot deleted the renovate/npm-vite-vulnerability branch April 1, 2025 20:56

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.4 [security] - autoclosed~~ chore(deps): update dependency vite to v6.2.4 [security] Apr 4, 2025

renovate bot reopened this Apr 4, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 3567edc to f3d8262 Compare April 4, 2025 19:07

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.4 [security]~~ chore(deps): update dependency vite to v6.2.5 [security] Apr 4, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from f6f6343 to 95a257d Compare April 11, 2025 15:35

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.5 [security]~~ chore(deps): update dependency vite to v6.2.6 [security] Apr 11, 2025

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.6 [security]~~ chore(deps): update dependency vite to v6.2.6 [security] - autoclosed Apr 13, 2025

renovate bot closed this Apr 13, 2025

renovate bot changed the title ~~chore(deps): update dependency vite to v6.2.6 [security] - autoclosed~~ chore(deps): update dependency vite to v6.2.6 [security] Apr 13, 2025

renovate bot reopened this Apr 13, 2025

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 8 times, most recently from 72fff44 to 6190093 Compare April 17, 2025 11:45

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 4 times, most recently from a7fd6fb to 79f4d35 Compare April 22, 2025 05:37

chore(deps): update dependency vite to v6.2.6 [security]

bb7a601

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 79f4d35 to bb7a601 Compare April 22, 2025 12:27

philibea merged commit 3c4356c into main Apr 22, 2025
5 of 6 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency vite to v6.2.6 [security] #2526

chore(deps): update dependency vite to v6.2.6 [security] #2526

Uh oh!

renovate bot commented Mar 25, 2025 •

edited

Loading

Uh oh!

changeset-bot bot commented Mar 25, 2025 •

edited

Loading

Uh oh!

codecov bot commented Mar 25, 2025 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chore(deps): update dependency vite to v6.2.6 [security] #2526

chore(deps): update dependency vite to v6.2.6 [security] #2526

Uh oh!

Conversation

renovate bot commented Mar 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

GitHub Vulnerability Alerts

Summary

Impact

Details

PoC

Summary

Impact

Details

PoC

Summary

Impact

Details

.svg

relative paths

PoC

Summary

Impact

Details

PoC

Release Notes

Configuration

Uh oh!

changeset-bot bot commented Mar 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

codecov bot commented Mar 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

renovate bot commented Mar 25, 2025 •

edited

Loading

`.svg`

changeset-bot bot commented Mar 25, 2025 •

edited

Loading

codecov bot commented Mar 25, 2025 •

edited

Loading