Skip to content

fix(deps): bump vitest to 3.2.6 (CVE-2026-47429) - #4

Open
devtechedge wants to merge 1 commit into
mainfrom
security/vitest-3-2-6
Open

devtechedge wants to merge 1 commit into
mainfrom
security/vitest-3-2-6

Conversation

@devtechedge

Copy link
Copy Markdown
Owner

Bumps vitest from ^2.1.9 to ^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 --ui is run. This repository does not install @vitest/ui and its test script is vitest 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 --host run 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 runs npm ci, npm test, npm run typecheck and 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.

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.
@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
synthesis Ready Ready Preview Sep 15, 2026 11:51pm UTC

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.

1 participant