Skip to content

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

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

chore(deps): update dependency vitest to v4 [security]#1157
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 1, 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.4^4.1.0 age confidence

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

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • At any time (no schedule defined)
  • 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 added the security label Jun 1, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 47824c3 to d2a619b Compare June 1, 2026 22:36
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 1, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d2a619b to 355ae97 Compare June 2, 2026 00:10
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 355ae97 to 59d69fd Compare June 2, 2026 00:21
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 59d69fd to 289423a Compare June 2, 2026 01:16
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 289423a to 6524deb Compare June 2, 2026 04:58
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 6524deb to ae32607 Compare June 2, 2026 16:20
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ae32607 to 70ea9f5 Compare June 2, 2026 16:30
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 2, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 24cca53 to bddc092 Compare June 2, 2026 23:02
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from bddc092 to e6578cc Compare June 2, 2026 23:10
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e6578cc to d5be0ad Compare June 2, 2026 23:20
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d5be0ad to fee63c0 Compare June 3, 2026 00:36
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 3, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from fee63c0 to a81f41d Compare June 3, 2026 00:39
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 3, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 3, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a81f41d to 41f17cc Compare June 3, 2026 03:00
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 3, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 6be1456 to 7b8d896 Compare June 3, 2026 14:01
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 3, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 3, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 791f1bc to 472a236 Compare June 3, 2026 23:08
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 3, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 472a236 to 4773f28 Compare June 4, 2026 00:29
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4773f28 to 302c692 Compare June 4, 2026 02:05
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 302c692 to 31c1831 Compare June 4, 2026 02:55
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 31c1831 to dd448d5 Compare June 4, 2026 02:57
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from dd448d5 to b3a2656 Compare June 4, 2026 03:07
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 99f8467 to 834ac53 Compare June 4, 2026 06:02
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 0d1e79e to ecede20 Compare June 4, 2026 07:27
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ecede20 to 36cd416 Compare June 4, 2026 07:39
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to ^3.2.6 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 36cd416 to 91750af Compare June 4, 2026 08:35
@renovate renovate Bot changed the title chore(deps): update dependency vitest to ^3.2.6 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant