fix(deps): bump vitest to 3.2.6 (CVE-2026-47429) - #4
Open
devtechedge wants to merge 1 commit into
Open
devtechedge wants to merge 1 commit into
devtechedge wants to merge 1 commit into
Conversation
Vitest UI server allows arbitrary file read and execution (GHSA-5xrq-8626-4rwp, CVSS 9.8). This is a major 2.x -> 3.x bump on a development-only dependency.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
vitestfrom^2.1.9to^3.2.6.Advisory
GHSA-5xrq-8626-4rwp / CVE-2026-47429 (critical, CVSS 9.8) - when the Vitest UI server is listening, an arbitrary file can be read and executed. Network attack vector, no authentication, no user interaction.
Honest assessment of exposure
Exposure today is low. The vulnerable component is the Vitest UI server, which only listens when
vitest --uiis run. This repository does not install@vitest/uiand its test script isvitest run, so the server never starts. Nothing in CI exposes it either.It is still worth closing: it is the last critical alert in the audit, the vulnerable code ships inside the package, and a future
--ui --hostrun would open a genuine unauthenticated RCE.Verification
Lockfile-only bump generated with
npm install --package-lock-only. The unit tests were not run locally, because a full install here takes 15-25 minutes. CI runsnpm ci,npm test,npm run typecheckand the Playwright e2e suite, so it will confirm this properly.This is a major 2.x -> 3.x bump. Merge only if CI is green.