Skip to content

chore(deps): update dependency vitest to v4 [security]#1911

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability
Open

chore(deps): update dependency vitest to v4 [security]#1911
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jun 2, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^3.2.0^4.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


When Vitest UI server is listening, arbitrary file can be read and executed

CVE-2026-47429 / GHSA-5xrq-8626-4rwp

More information

Details

Summary

Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.

Impact

Only users that match either of the following conditions are affected:

  • explicitly exposes the Vitest UI server to the network (using --api.host or api.host config option)
  • running the Vitest UI or Browser Mode on Windows
Details

The API handler for /__vitest_attachment__ uses the deprecated isFileServingAllowed incorrectly.
https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
The function expects the passed value to use cleanUrl after the check before file system related operation.
Because of this, it is possible to bypass the check by \\?\\..\\. This is not possible on Linux as Linux errors if a directory named ? does not exist.

A similar problem exists in other places as well.

That said, this isFileServingAllowed check does not actually prevent the API to be abused. Since the API has rerun feature and file write feature, it's possible to run arbitrary script by writing a script as a test file using saveTestFile and running it using rerun. This means exposing the API / Vitest UI is equivalent to giving script execution access.
On the browser mode side, there're readFile / writeFile / saveSnapshotFile. So exposing the browser mode is equivalent to giving file read / write access.

PoC
  1. Run Vitest UI
  2. Get the API token by curl http://localhost:51204/__vitest__/
  3. Run curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&contentType=text/plain&token=$TOKEN" (TOKEN is the API token)
  4. curl shows the content of secret.txt that is outside the project directory
Mitigations

Vitest now ships two configuration flags, allowWrite and allowExec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-localhost host, ensuring that exposing the server to the network no longer implicitly grants write or execute capabilities to remote clients.

When these flags are disabled, the UI also enters a read-only mode: in-browser code editing and test file execution are turned off, removing the attack surface that allowed remote code execution. Many Browser Mode features are also disabled, like attachments, artifacts or snapshots. See browser.api.

Users who require the full interactive UI on a networked host must explicitly opt in by setting allowWrite and/or allowExec to true.

Severity

  • CVSS Score: 9.8 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vitest-dev/vitest (vitest)

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.18

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.17

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.16

Compare Source

   🐞 Bug Fixes
  • Fix browser mode default testTimeout back to 15 seconds  -  by [@​hi-ogawa](https://redirect.gi

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR becomes conflicted, 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.

@renovate renovate Bot requested a review from a team as a code owner June 2, 2026 03:02
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jun 2, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitest/coverage-v8@3.2.4
npm error Found: vitest@4.1.8
npm error node_modules/vitest
npm error   dev vitest@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"3.2.4" from @vitest/coverage-v8@3.2.4
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"^3.2.0" from the root project
npm error
npm error Conflicting peer dependency: vitest@3.2.4
npm error node_modules/vitest
npm error   peer vitest@"3.2.4" from @vitest/coverage-v8@3.2.4
npm error   node_modules/@vitest/coverage-v8
npm error     dev @vitest/coverage-v8@"^3.2.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-02T03_01_10_289Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-02T03_01_10_289Z-debug-0.log

File name: pnpm-lock.yaml
Scope: all 22 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 20, reused 0, downloaded 0, added 0

   ╭─────────────────────────────────────────╮
   │                                         │
   │   Update available! 11.0.1 → 11.5.0.    │
   │   Changelog: https://pnpm.io/v/11.5.0   │
   │    To update, run: pnpm add -g pnpm     │
   │                                         │
   ╰─────────────────────────────────────────╯

Progress: resolved 26, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated rolldown-vite@7.3.1
Progress: resolved 34, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 0, added 0
 WARN  The metadata of react is missing the "time" field; skipping the minimumReleaseAge check for this package.
 WARN  The metadata of react-dom is missing the "time" field; skipping the minimumReleaseAge check for this package.
 WARN  The metadata of @radix-ui/react-slot is missing the "time" field; skipping the minimumReleaseAge check for this package.
Progress: resolved 52, reused 0, downloaded 0, added 0
Progress: resolved 53, reused 0, downloaded 0, added 0
Progress: resolved 54, reused 0, downloaded 0, added 0
Progress: resolved 60, reused 0, downloaded 0, added 0
 WARN  The metadata of react-aria is missing the "time" field; skipping the minimumReleaseAge check for this package.
packages/drawer                          |  WARN  deprecated @launchpad-ui/progress@0.5.57
Progress: resolved 64, reused 0, downloaded 0, added 0
packages/navigation                      |  WARN  deprecated @launchpad-ui/chip@0.9.58
Progress: resolved 66, reused 0, downloaded 0, added 0
Progress: resolved 73, reused 0, downloaded 0, added 0
Progress: resolved 79, reused 0, downloaded 0, added 0
Progress: resolved 80, reused 0, downloaded 0, added 0
Progress: resolved 82, reused 0, downloaded 0, added 0
 WARN  The metadata of @changesets/types is missing the "time" field; skipping the minimumReleaseAge check for this package.
Progress: resolved 153, reused 0, downloaded 0, added 0
Progress: resolved 179, reused 0, downloaded 0, added 0
Progress: resolved 250, reused 0, downloaded 0, added 0
Progress: resolved 262, reused 0, downloaded 0, added 0
Progress: resolved 280, reused 0, downloaded 0, added 0
 WARN  The metadata of @vitest/expect is missing the "time" field; skipping the minimumReleaseAge check for this package.
Progress: resolved 343, reused 0, downloaded 0, added 0
Progress: resolved 372, reused 0, downloaded 0, added 0
Progress: resolved 394, reused 0, downloaded 0, added 0
Progress: resolved 439, reused 0, downloaded 0, added 0
Progress: resolved 519, reused 0, downloaded 0, added 0
Progress: resolved 570, reused 0, downloaded 0, added 0
Progress: resolved 579, reused 0, downloaded 0, added 0
Progress: resolved 674, reused 0, downloaded 0, added 0
Progress: resolved 707, reused 0, downloaded 3, added 0
Progress: resolved 745, reused 0, downloaded 3, added 0
 WARN  The metadata of react-is is missing the "time" field; skipping the minimumReleaseAge check for this package.
Progress: resolved 837, reused 0, downloaded 3, added 0
Progress: resolved 990, reused 0, downloaded 3, added 0
Progress: resolved 1041, reused 0, downloaded 3, added 0
 WARN  8 deprecated subdependencies found: git-raw-commits@4.0.0, glob@10.4.5, glob@10.5.0, glob@7.2.3, inflight@1.0.6, rimraf@2.7.1, string-at@1.1.0, whatwg-encoding@3.1.1
Progress: resolved 1060, reused 0, downloaded 3, added 0
Progress: resolved 1060, reused 0, downloaded 3, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

hint: Run "pnpm peers check" to list the peer dependency issues.
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false


@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jun 2, 2026

⚠️ No Changeset found

Latest commit: f008e05

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

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit f008e05. Configure here.

Comment thread package.json
"typescript-plugin-css-modules": "^5.1.0",
"vite": "npm:rolldown-vite@7.3.1",
"vitest": "^3.2.0"
"vitest": "^4.0.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Companion @vitest packages not updated with vitest major bump

High Severity

vitest is bumped to ^4.0.0 but @vitest/coverage-v8 and @vitest/ui remain at ^3.2.0. These companion packages declare vitest: 3.2.0 as a peer dependency, and the workspace enforces strictPeerDependencies: true, so pnpm install will fail with a peer dependency conflict. Both packages need to be updated to ^4.0.0 to match.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit f008e05. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants