Skip to content

chore(deps): update dependency vitest to v3 [security]#3

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

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

Conversation

@renovate

@renovate renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^2.0.0^3.2.6 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)

v3.2.6

Compare Source

v3.2.5

Compare Source

v3.2.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.1.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.2

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source

🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub

v3.0.9

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.7

Compare Source

   🐞 Bug Fixes
  • browser: Support webdriverio 9  -  by [@&#820

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

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

@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ COPYPASTE jscpd yes no no 1.82s
✅ EDITORCONFIG editorconfig-checker 1 0 0 0.22s
✅ JSON jsonlint 1 0 0 0.39s
✅ JSON npm-package-json-lint yes no no 0.34s
✅ JSON v8r 1 0 0 8.34s
✅ REPOSITORY git_diff yes no no 0.21s
✅ REPOSITORY secretlint yes no no 0.72s
✅ REPOSITORY syft yes no no 3.27s
✅ REPOSITORY trivy yes no no 9.16s
✅ REPOSITORY trivy-sbom yes no no 1.26s
✅ REPOSITORY trufflehog yes no no 23.37s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 703fef2 to a6444ae Compare June 8, 2026 20:03
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a6444ae to 3ae37f4 Compare June 8, 2026 20:03
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3ae37f4 to 11ca1e6 Compare June 8, 2026 20:45
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 11ca1e6 to 6adc652 Compare June 8, 2026 20:45
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 6adc652 to 18df2dc Compare June 8, 2026 21:00
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 18df2dc to ad1bc04 Compare June 8, 2026 21:00
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ad1bc04 to da84d9a Compare June 8, 2026 21:17
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from da84d9a to f764208 Compare June 8, 2026 21:18
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f764208 to c835d2a Compare June 8, 2026 21:22
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c835d2a to 2c47de9 Compare June 8, 2026 21:44
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2c47de9 to 2d9c665 Compare June 8, 2026 21:45
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2d9c665 to 7b4903b Compare June 8, 2026 22:19
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7b4903b to 4847c50 Compare June 8, 2026 22:23
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4847c50 to a23c380 Compare June 8, 2026 22:25
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a23c380 to dbb8d28 Compare June 8, 2026 22:26
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from dbb8d28 to bb859d8 Compare June 8, 2026 22:35
@renovate renovate Bot changed the title Update dependency vitest to v3 [SECURITY] chore(deps): update dependency vitest to v4 [security] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from bb859d8 to b7c892d Compare June 8, 2026 22:38
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b7c892d to a70f00d Compare June 8, 2026 22:43
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a70f00d to 3294fc8 Compare June 9, 2026 01:48
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3294fc8 to 2c302f6 Compare June 9, 2026 13:26
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2c302f6 to 042dadb Compare June 9, 2026 13:27
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 042dadb to 67c2839 Compare June 9, 2026 22:15
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 67c2839 to f8adda2 Compare June 9, 2026 22:33
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f8adda2 to 0409662 Compare June 9, 2026 22:35
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0409662 to 7de34cc Compare June 9, 2026 22:36
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7de34cc to 5db906a Compare June 9, 2026 22:57
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Jun 9, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 5db906a to 40846f1 Compare June 10, 2026 01:50
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 10, 2026
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