-
Couldn't load subscription status.
- Fork 0
chore(deps): update dependency vitest to v1.6.1 [security] #49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
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
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
May 24, 2025 15:33
0dd94cb to
060312e
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
June 6, 2025 12:01
34acb1b to
63a7d8f
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
June 29, 2025 11:59
63a7d8f to
c3c867e
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
July 6, 2025 12:09
c3c867e to
59de750
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
2 times, most recently
from
August 15, 2025 11:57
84c2e69 to
dc97c29
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
August 23, 2025 15:57
dc97c29 to
80a4af9
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
September 1, 2025 03:59
80a4af9 to
ecbdb6a
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
September 26, 2025 15:51
ecbdb6a to
f62a503
Compare
@renovate
renovate
bot
force-pushed
the
renovate/npm-vitest-vulnerability
branch
from
October 25, 2025 04:12
f62a503 to
f9cbfd8
Compare
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.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
1.5.0->1.6.1GitHub Vulnerability Alerts
CVE-2025-24964
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.
Release Notes
vitest-dev/vitest (vitest)
v1.6.1Compare Source
This release includes security patches for:
🐞 Bug Fixes
View changes on GitHub
v1.6.0Compare Source
🚀 Features
includeConsoleOutputandaddFileAttributein junit - by @hi-ogawa in #5659 (2f913)🐞 Bug Fixes
resolveId('vitest')afterbuildStart- by @hi-ogawa in #5646 (f5faf)toJSONfor error serialization - by @hi-ogawa in #5526 (19a21)*.test-d.*by default - by @MindfulPol in #5634 (bfe8a)vite-node's wrapper only to executed files - by @AriPerkkio in #5642 (c9883)🏎 Performance
View changes on GitHub
v1.5.3Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.5.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.5.1Compare Source
🚀 Features
startVitest()to acceptstdoutandstdin- by @AriPerkkio in #5493 (780b1)startVitestAPI is experimental and doesn't follow semver.🐞 Bug Fixes
import.meta.env.PROD: false- by @hi-ogawa in #5561 (9c649)onTestFinishedin reverse order - by @sheremet-va in #5598 (23f29)fileParallelismby default on browser pool - by @hi-ogawa in #5528 (5c69f)v8-to-istanbul- by @AriPerkkio in #5549 (df6a4)cleanOnRerunis disabled - by @AriPerkkio in #5540 (ea3c1)thresholdsto compare files relative to root - by @AriPerkkio in #5574 (80265)toEqualandtoMatchObjectwith circular references - by @hi-ogawa in #5535 (9e641)View changes on GitHub
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 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.