| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
✅ Meticulous spotted 0 visual differences across 290 screens tested: view results. Meticulous evaluated ~4 hours of user flows against your PR. Expected differences? Click here. Last updated for commit 4aaabf2 chore(deps): update dependency vitest to v3 [security]. This comment will update as new commits are pushed. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR contains the following updates:
When Vitest UI server is listening, arbitrary file can be read and executed
CVE-2026-47429 / GHSA-5xrq-8626-4rwp
More informationDetails
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:
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
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
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
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.