Security Fix: Upgrade vitest to Address Critical RCE Vulnerability (CVE-2025-24964) #451
Conversation
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.
Hi team,
During a review using Semgrep, I identified a critical security vulnerability affecting this repository's development dependencies.
Issue: vitest@2.1.1 is affected by CVE-2025-24964, which allows Remote Code Execution (RCE) via Cross-site WebSocket Hijacking (CSWSH) when the Vitest API server is running and a developer visits a malicious website.
Severity: Critical — no origin validation allows arbitrary WebSocket connections to trigger test runner commands and potentially execute arbitrary code on a dev machine.
Likelihood: Medium to High. Many dev setups run vitest --watch or enable its UI/API server by default. Exploitation only requires a developer to visit a malicious website while the test server is active.
Recommended Fix: Upgrade to vitest >= 2.1.9 (or preferably 3.0.5) where this issue has been patched.