chore(deps): update dependency vite to v6.1.5 [security] #6418

renovate · 2025-03-25T20:04:25Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`6.1.1` -> `6.1.5`

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.1.5`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.1.4`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.1.3`

Compare Source

Please refer to CHANGELOG.md for details.

`v6.1.2`

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-25T20:04:31Z

⚠️ No Changeset found

Latest commit: 7a6f137

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

netlify · 2025-03-25T20:04:43Z

✅ Deploy Preview for mermaid-js ready!

Name	Link
🔨 Latest commit	`3eff588`
🔍 Latest deploy log	https://app.netlify.com/sites/mermaid-js/deploys/67f61a068a420f00089c7860
😎 Deploy Preview	https://deploy-preview-6418--mermaid-js.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

pkg-pr-new · 2025-03-25T20:05:41Z

Open in StackBlitz

npm i https://pkg.pr.new/mermaid-js/mermaid@6418

npm i https://pkg.pr.new/mermaid-js/mermaid/@mermaid-js/layout-elk@6418

npm i https://pkg.pr.new/mermaid-js/mermaid/@mermaid-js/mermaid-zenuml@6418

npm i https://pkg.pr.new/mermaid-js/mermaid/@mermaid-js/parser@6418

commit: 7a6f137

codecov · 2025-03-25T20:07:12Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 3.87%. Comparing base (9d838d4) to head (7a6f137).

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #6418   +/-   ##
=======================================
  Coverage     3.87%   3.87%           
=======================================
  Files          412     412           
  Lines        43134   43134           
  Branches       664     664           
=======================================
  Hits          1672    1672           
  Misses       41462   41462

Flag	Coverage Δ
unit	`3.87% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

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

netlify · 2025-04-09T07:53:23Z

✅ Deploy Preview for mermaid-js ready!

Name	Link
🔨 Latest commit	`7a6f137`
🔍 Latest deploy log	https://app.netlify.com/sites/mermaid-js/deploys/6802358cd4936e0008af3d34
😎 Deploy Preview	https://deploy-preview-6418--mermaid-js.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from 2728a62 to 11ee16d Compare March 31, 2025 19:36

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

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 3 times, most recently from f1f84cd to f64a019 Compare April 4, 2025 15:49

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

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 10 times, most recently from 3eff588 to 597e08e Compare April 9, 2025 07:52

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 5 times, most recently from 3458716 to 1e23816 Compare April 11, 2025 15:10

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

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from c314cc8 to 0c5e063 Compare April 14, 2025 06:17

renovate bot force-pushed the renovate/npm-vite-vulnerability branch 13 times, most recently from 79ad0ec to df81db4 Compare April 18, 2025 09:15

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

7a6f137

renovate bot force-pushed the renovate/npm-vite-vulnerability branch from df81db4 to 7a6f137 Compare April 18, 2025 11:20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency vite to v6.1.5 [security] #6418

chore(deps): update dependency vite to v6.1.5 [security] #6418

renovate bot commented Mar 25, 2025 •

edited

Loading

changeset-bot bot commented Mar 25, 2025 •

edited

Loading

netlify bot commented Mar 25, 2025 •

edited

Loading

pkg-pr-new bot commented Mar 25, 2025 •

edited

Loading

codecov bot commented Mar 25, 2025 •

edited

Loading

netlify bot commented Apr 9, 2025 •

edited

Loading

chore(deps): update dependency vite to v6.1.5 [security] #6418

Are you sure you want to change the base?

chore(deps): update dependency vite to v6.1.5 [security] #6418

Conversation

renovate bot commented Mar 25, 2025 • edited Loading

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

changeset-bot bot commented Mar 25, 2025 • edited Loading

⚠️ No Changeset found

netlify bot commented Mar 25, 2025 • edited Loading

✅ Deploy Preview for mermaid-js ready!

pkg-pr-new bot commented Mar 25, 2025 • edited Loading

codecov bot commented Mar 25, 2025 • edited Loading

Codecov Report

netlify bot commented Apr 9, 2025 • edited Loading

✅ Deploy Preview for mermaid-js ready!

renovate bot commented Mar 25, 2025 •

edited

Loading

`.svg`

changeset-bot bot commented Mar 25, 2025 •

edited

Loading

netlify bot commented Mar 25, 2025 •

edited

Loading

pkg-pr-new bot commented Mar 25, 2025 •

edited

Loading

codecov bot commented Mar 25, 2025 •

edited

Loading

netlify bot commented Apr 9, 2025 •

edited

Loading