Update dependency vitest to v2.1.9 [SECURITY] - #12
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Reviewer's Guide by SourceryThis PR updates the vitest dependency from v2.0.1 to v2.1.9 to address a security vulnerability (CVE-2025-24964) that allows for arbitrary remote code execution when the Sequence diagram showing the security vulnerability in Vitest v2.0.1sequenceDiagram
actor Attacker
participant MW as Malicious Website
participant WS as WebSocket Server
participant VF as Vitest File System
participant TS as Test Suite
Note over WS: No Origin check or auth
Attacker->>MW: Visits malicious site
MW->>WS: Connect to ws://localhost:51204/__vitest_api__
MW->>WS: Request file list
WS-->>MW: Return test files
MW->>WS: saveTestFile with malicious code
WS->>VF: Write malicious code
MW->>WS: rerun command
WS->>TS: Execute modified test file
TS->>TS: Execute arbitrary code
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
February 9, 2025 11:46
9580561 to
5dac859
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
March 5, 2025 03:45
5dac859 to
cb5cb0b
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
3 times, most recently
from
March 18, 2025 08:00
c86605c to
bc74b37
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
April 2, 2025 19:50
bc74b37 to
8207e63
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
April 12, 2025 04:05
8207e63 to
e066638
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
April 27, 2025 03:50
e066638 to
a7a877a
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
May 24, 2025 11:59
a7a877a to
9398b89
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
June 6, 2025 17:16
642d688 to
87cb5f3
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
July 5, 2025 04:02
87cb5f3 to
4f73d27
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
August 15, 2025 11:50
6206b44 to
36b70d7
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
August 24, 2025 00:06
36b70d7 to
3d7bc27
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
September 26, 2025 12:04
3d7bc27 to
8aa1d35
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
October 23, 2025 19:28
8aa1d35 to
14bbfb1
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
November 19, 2025 03:29
e589a9b to
7b4dab5
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
December 4, 2025 20:14
7b4dab5 to
d941e86
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
January 1, 2026 20:08
d941e86 to
2094a5b
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
January 9, 2026 12:15
2094a5b to
0e26d98
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
January 20, 2026 03:56
0e26d98 to
08c3911
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
February 3, 2026 19:46
08c3911 to
b76926f
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
February 13, 2026 20:15
b76926f to
2250fa6
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
March 14, 2026 17:22
4e4d9d3 to
7c5e40c
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
April 15, 2026 11:39
7c5e40c to
9e99c50
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
May 1, 2026 07:38
9e99c50 to
3d738ff
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
May 13, 2026 20:15
3d738ff to
d596e7e
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
May 22, 2026 03:27
d596e7e to
b137083
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
June 4, 2026 04:01
d9faa69 to
b37fad7
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
June 12, 2026 14:45
b37fad7 to
173c094
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
July 18, 2026 00:06
173c094 to
6bdc921
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
July 25, 2026 12:00
6bdc921 to
5459186
Compare
renovate
Bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
August 1, 2026 11:45
5459186 to
8805af4
Compare
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.
This PR contains the following updates:
2.0.1→2.1.9Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening
CVE-2025-24964 / GHSA-9crc-q9x8-hgqq
More information
Details
Summary
Arbitrary remote Code Execution when accessing a malicious website while Vitest API server is listening by Cross-site WebSocket hijacking (CSWSH) attacks.
Details
When
apioption is enabled (Vitest UI enables it), Vitest starts a WebSocket server. This WebSocket server did not check Origin header and did not have any authorization mechanism and was vulnerable to CSWSH attacks.https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L32-L46
This WebSocket server has
saveTestFileAPI that can edit a test file andrerunAPI that can rerun the tests. An attacker can execute arbitrary code by injecting a code in a test file by thesaveTestFileAPI and then running that file by calling thererunAPI.https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L66-L76
PoC
calcexecutable inPATHenv var (you'll likely have it if you are running on Windows), that application will be executed.Impact
This vulnerability can result in remote code execution for users that are using Vitest serve API.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vitest-dev/vitest (vitest)
v2.1.9Compare Source
This release includes security patches for:
🐞 Bug Fixes
/__screenshot-error- by @hi-ogawa in #7343View changes on GitHub
v2.1.8Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.7Compare Source
🐞 Bug Fixes
pnpm.overridesor yarn resolutions to override theviteversion in thevitestpackage - the APIs are compatible.View changes on GitHub
v2.1.6Compare Source
🚀 Features
View changes on GitHub
v2.1.5Compare Source
🐞 Bug Fixes
dangerouslyIgnoreUnhandledErrorswithout base reporter - by @AriPerkkio in #6808 (0bf0a)unhandledRejectioneven when base reporter is not used - by @AriPerkkio in #6812 (8878b)sequence.concurrentfrom theRuntimeConfigtype - by @sheremet-va in #6880 (6af73).poll,.element,.rejects/.resolves, andlocator.*weren't awaited - by @sheremet-va in #6877 (93b67)enteror'a'- by @AriPerkkio in #6848 (487c8)🏎 Performance
View changes on GitHub
v2.1.4Compare Source
🚀 Features
This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your
package.json. See npm's documentation about semver for more information.transformIndexHtml- by @sheremet-va in #6725 (16902)🐞 Bug Fixes
v=queries to setup files imports - by @sheremet-va in #6759 (b8258)toThrowErrorwith empty string parameter - by @shulaoda in #6710 (a6129)test.extendtype exports - by @hi-ogawa in #6707 (e5c38)🏎 Performance
hashto replacecreateHash- by @btea in #6703 (5d07b)View changes on GitHub
v2.1.3Compare Source
🐞 Bug Fixes
toBeNaN, toBeUndefined, toBeNull, toBeTruthy, toBeFalsy- by @hi-ogawa in #6697 (e0027)/mockServiceWorker.jsinstead of/__vitest_msw__- by @sheremet-va in #6687 (4b2ce)toMatchObjectdiff - by @hi-ogawa in #6620 (d289e)<empty line>logs when interleavingconsole.log/error- by @hi-ogawa in #6644 (9ece3)fast-globinstead oftinyglobbyin Vitest - by @sheremet-va in #6688 (70baa)🏎 Performance
View changes on GitHub
v2.1.2Compare Source
🐞 Bug Fixes
Vitest.setServerto postconfigureServerhook to enable import analysis for workspace config loading - by @hi-ogawa in #6584 (e7f35)BenchmarkResult.samplesarray to reduce memory usage - by @hi-ogawa and @AriPerkkio in #6541 (a6407)data:protocol on preview provider file upload - by @userquin in #6501 (e9821)*.astroby default - by @AriPerkkio in #6565 (f8ff7)cleanOnRerun: falseto invalidate previous results - by @AriPerkkio in #6592 (88bde)toBeDefinedwithexpect.poll- by @hi-ogawa in #6562 (f7da6)--cpu-profand--heap-profnot working by default - by @AriPerkkio in #6555 (2e4d894)beforeAllfailed - by @hi-ogawa in #6524 (fb797)onTestFinishedandonTestFailedduringretryandrepeats- by @hi-ogawa in #6609 (c5e29)--standalone- by @hi-ogawa in #6577 (d0bf8)View changes on GitHub
v2.1.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.0Compare Source
This release makes another big change to the Browser Mode by introducing locators API:
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the
pageobject from@vitest/browser/context.Potential Breaking Change
vitest.config.tsorvite.config.tsinside the folder)projects/*will match anything inside theprojectsfolder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config.projects/**/*previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.🚀 Features
userEvent.uploadin playwright provider - by @sheremet-va in #6442 (cf148)--inspect- by @AriPerkkio in #6433 (0499a)--inspect-brk- by @AriPerkkio in #6434 (7ab0f)--exclude-after-remap- by @AriPerkkio in #6309 (5932a){ spy: true }instead of a factory - by @sheremet-va in #6289 (95f02)vi.advanceTimersToNextFrame- by @bnjm and @sheremet-va in #6347 (8ff63)fast-globtotinyglobby- by @SuperchupuDev in #6274 (c321a)🐞 Bug Fixes
indexfile - by @sheremet-va in #6266 (081cf)expect.getState().testPathalways returns correct path - by @sheremet-va in #6472 (ac698)vitestand@vitest/*versions don't match - by @AriPerkkio in #6317 (e662c)vitenodefor uncovered files - by @AriPerkkio in #6044 (da52d)performance.nowinstead ofDate.nowfor duration - by @LuciNyan in #6382 (fe489)toMatchInlineSnapshotupdates at the same location - by @hi-ogawa in #6332 (1606f)typecheck.includeoverlaps withinclude- by @sheremet-va in #6256 (153ff)View changes on GitHub
v2.0.5Compare Source
🚀 Features
🐞 Bug Fixes
testNamePatternadds leading space - by @AriPerkkio in #6186 (073a5)afterEachcleanup hooks in node entrypoint - by @sheremet-va in #6192 (e6fbc)defineProjectanddefineWorkspacetypes - by @sheremet-va in #6198 (8cd82)node:*imports in__mocks__folder - by @sheremet-va in #6204 (a48be)View changes on GitHub
v2.0.4Compare Source
🐞 Bug Fixes
require- by @sheremet-va in #6159 (807a2)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.