chore(monorepo): update dependency vitest to v3.2.6 [security]#1537
chore(monorepo): update dependency vitest to v3.2.6 [security]#1537renovate[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 744 in 95302ba
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🧹 Starting cleanup of preview environment resources... |
|
✅ Preview environment cleanup success. Cleanup Status:
|
95302ba to
4f3895d
Compare
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
4f3895d to
08b69a3
Compare
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
08b69a3 to
de72918
Compare
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6765 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6778 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6791 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6858 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6868 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6877 in de72918
There was a problem hiding this comment.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6886 in de72918
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
de72918 to
62a4157
Compare
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
|
🔄 Preview deployment started... Please wait while we deploy your changes! |
|
❌ Preview deployment failure. Deployment failed. Please check the workflow logs for more details. |
This PR contains the following updates:
3.2.4→3.2.6When 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:
--api.hostorapi.hostconfig option)Details
The API handler for
/__vitest_attachment__uses the deprecatedisFileServingAllowedincorrectly.https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
The function expects the passed value to use
cleanUrlafter 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
isFileServingAllowedcheck 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 usingsaveTestFileand running it usingrerun. 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
curl http://localhost:51204/__vitest__/curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&contentType=text/plain&token=$TOKEN"(TOKEN is the API token)secret.txtthat is outside the project directoryMitigations
Vitest now ships two configuration flags,
allowWriteandallowExec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-localhosthost, 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
allowWriteand/orallowExectotrue.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vitest-dev/vitest (vitest)
v3.2.6Compare Source
v3.2.5Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.