fix(deps): bump vitest to 4.1.x (CVE-2026-47429)#78
Merged
Conversation
vitest <4.1.0 allows arbitrary file read/execute when the Vitest UI server is listening (CVE-2026-47429, GHSA-5xrq-8626-4rwp). The only patched release is 4.1.0; there is no 2.x/3.x backport. frontend and backend were on 4.0.16, so this is a small in-major bump (resolves to 4.1.8). Local tests green: frontend 29/29, backend 69/69. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jz-inworld
force-pushed
the
jz/sec-vitest-cve-2026-47429
branch
from
1f15614 to
69e0486
Compare
There was a problem hiding this comment.
Pull request overview
Bumps vitest (and @vitest/coverage-v8) from ^4.0.16 to ^4.1.0 in both frontend/ and backend/ to address CVE-2026-47429, which allows arbitrary file read/execution through the Vitest UI server. Lockfiles re-resolve to vitest 4.1.8, with churn from vitest's internal switch from Rollup/esbuild to Rolldown/lightningcss in test-only transitive dependencies.
Changes:
- Bump
vitestto^4.1.0infrontend/package.jsonandbackend/package.json - Bump
@vitest/coverage-v8to^4.1.0inbackend/package.json - Re-resolve lockfiles to vitest 4.1.8 with associated transitive dependency updates
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| frontend/package.json | Bumps vitest devDependency to ^4.1.0 |
| frontend/package-lock.json | Re-resolved lockfile reflecting vitest 4.1.8 and transitive dependency churn |
| backend/package.json | Bumps vitest and @vitest/coverage-v8 devDependencies to ^4.1.0 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Gugic
approved these changes
Jun 1, 2026
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.
What
Bumps
vitest(and@vitest/coverage-v8in backend) from^4.0.16to^4.1.0infrontend/andbackend/. Lockfiles re-resolve to vitest 4.1.8.Why
vitest below 4.1.0 has a critical flaw (CVE-2026-47429 / GHSA-5xrq-8626-4rwp): when the Vitest UI server is listening, an attacker can read and execute arbitrary files. The only fixed release is 4.1.0, there is no 2.x/3.x backport. Both packages were on 4.0.16, so this is a small in-major bump.
Note on lockfile size
The backend
package-lock.jsonchurns a lot because vitest 4.1 swapped its internal bundler from Rollup/esbuild to Rolldown/lightningcss. The removed@rollup/*/esbuild platform binaries and added@rolldown/*/lightningcss-*entries are test-only transitive deps (never shipped).lockfileVersionis unchanged.Verification
Local
npm testgreen on 4.1.8:Draft until CI confirms.