Update dependency vitest to v4.1.11 [SECURITY]

[matticbot]

This PR contains the following updates:

Package	Change	Age	Confidence
vitest (source)	4.1.10 → 4.1.11

---

Vitest: Path Traversal / Arbitrary File Read via @​vitest/mocker Redirect Mock

CVE-2026-84373 / GHSA-82fw-gwwq-j7x9

More information

Details

Summary

@vitest/mocker registers a redirect mock's target path without validating it
against the dev server's file-serving allowlist. An attacker who can reach the
dev server's WebSocket can register a redirect mock pointing outside the project
root; when the mocked module is requested, the plugin's load hook returns
readFile(<attacker path>) as the module source, disclosing local files.

This is exploitable without authentication only through the public
mockerPlugin / standalone interceptorPlugin exports (used by third-party dev
servers), which register the handler on Vite's unauthenticated HMR socket.
Vitest's own browser mode registers mocks over a token-authenticated RPC and
is not remotely reachable by default (see Scope).

Affected code

packages/mocker/src/node/interceptorPlugin.ts.

The load hook is the file-read sink:

if (mock.type === 'redirect') {
  return readFile(mock.redirect, 'utf-8')
}

mock.redirect is derived from client input at registration time with no
boundary check:

if (event.type === 'redirect') {
  const redirectUrl = new URL(event.redirect)
  event.redirect = join(server.config.root, redirectUrl.pathname)
}
registry.register(event)

There is no server.fs.allow / server.fs.deny check and no assertion that the
resolved path stays within the project root.

Registration paths and trust boundaries

• Public mockerPlugin / interceptorPlugin (unauthenticated). In
  configureServer, the plugin registers server.ws.on('vitest:interceptor:register', …)
  on Vite's HMR WebSocket. That socket performs no token, Origin, or same-origin
  check, so any client that can reach it can register a redirect mock. This is
  the path the "unauthenticated" impact applies to.
• Vitest browser mode (authenticated). Mocks register over the browser RPC
  (registerMock), which sits behind a per-run token (isValidApiRequest, a
  random api.token). The interceptor's configureServer socket is not used for
  registration here (in v5 it does not run at all, as the plugin is injected per
  environment). The same missing boundary check exists on the authenticated RPC
  path, but reaching it requires the token, so it is not a remote-unauthenticated
  read.

Path handling

new URL(redirect).pathname combined with join(root, pathname) does not
confine reads to the root:

• Special/hierarchical schemes (file:, http:) are normalized by WHATWG URL,
  so .. segments are collapsed and the result stays under the root. Payloads of
  the form file:///../../etc/passwd do not escape.
• A non-special (opaque) scheme preserves .. in pathname, so
  join(root, "../../…/etc/passwd") resolves outside the root and reads an
  arbitrary file.

Even without escaping the root, the missing server.fs check allows reading any
in-root file the dev server would otherwise refuse to serve (for example an
in-root .env or source that is denied by server.fs.deny).

Scope / preconditions

• This is a development-server issue. The dev server binds to localhost by
  default and is not reachable from the network unless the developer exposes it
  (server.host / 0.0.0.0, a LAN bind, or a proxy).
• A raw (non-browser) client against a reachable server bypasses browser origin
  and CORS protections entirely and can both register the mock and read the
  response.
• A browser-based drive-by against a localhost server is substantially mitigated
  by Vite defaults: the default CORS origin allowlist is limited to localhost
  origins, and server.allowedHosts blocks DNS-rebinding, so a cross-origin page
  cannot read the file contents back.

Impact

Disclosure of local files readable by the dev-server process (source, in-root
.env/secrets, and, via the opaque-scheme payload, files outside the project
root). No integrity or availability impact.

Affected versions

Present since @vitest/mocker was introduced.

• Affected: @vitest/mocker >= 2.1.0 (shipped in vitest and
  @vitest/browser >= 2.1.0), through 4.1.x and the 5.0.0 pre-releases.
• Fixed: Vitest 4.1.11 and 5.0.0. Older majors (2.1.x, 3.x) are not
  maintained and are not planned to receive the fix.

Fix

Validate the resolved redirect target against Vite's file-serving allowlist
(isFileLoadingAllowed) before registering it, at every registration site, and
stop registering the interceptor WebSocket events in Vitest's browser mode
(mocks there flow through the authenticated RPC).

Severity

• CVSS Score: Unknown
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/vitest-dev/vitest/security/advisories/GHSA-82fw-gwwq-j7x9
• https://nvd.nist.gov/vuln/detail/CVE-2026-84373
• https://github.com/vitest-dev/vitest/pull/10972
• https://github.com/vitest-dev/vitest/pull/10974
• https://github.com/vitest-dev/vitest/commit/51edf2b072902aec6d30c90ebaafd8f121c6f9d8
• https://github.com/vitest-dev/vitest/commit/8ff9b9a9efca7c6cfd5243569440de8d7a33aec4
• https://github.com/vitest-dev/vitest/commit/fe5a11d3ceac5ec10d6d7d21a46d4caca132c48f
• https://github.com/vitest-dev/vitest
• https://github.com/vitest-dev/vitest/releases/tag/v4.1.11
• https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-rc.2

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

---

Release Notes

vitest-dev/vitest (vitest)

v4.1.11

Compare Source

   🐞 Bug Fixes

• Revive global concurrency limit for test lifecycle [backport to v4]  -  by @​sheremet-va and @​hi-ogawa in #​10992 (5146d)
• browser:
  • Encode iframeId in tester iframe URL [backport to v4]  -  by @​sheremet-va, Pduhard and Claude Opus 4.8 in #​10955 (10b2c)
  • Trigger playwright/chromium gc on lower disk availability [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode in #​10951 (9851d)
• mocker:
  • Restrict redirect mocks to the fs allowlist [backport to v4]  -  by @​sheremet-va in #​10974 (fe5a1)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - "" in timezone 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.

---

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

---

This PR has been generated by Renovate Bot.

[matticbot]

⚠️ 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 111 workspace projects
? Verifying lockfile against supply-chain policies (2530 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 128, reused 0, downloaded 0, added 0
Progress: resolved 191, reused 0, downloaded 0, added 0
Progress: resolved 251, reused 0, downloaded 0, added 0
Progress: resolved 307, reused 0, downloaded 0, added 0
Progress: resolved 393, reused 0, downloaded 0, added 0
Progress: resolved 394, reused 0, downloaded 0, added 0
Progress: resolved 395, reused 0, downloaded 0, added 0
Progress: resolved 649, reused 0, downloaded 0, added 0
Progress: resolved 948, reused 0, downloaded 0, added 0
Progress: resolved 1106, reused 0, downloaded 0, added 0
Progress: resolved 1356, reused 0, downloaded 0, added 0
Progress: resolved 1359, reused 0, downloaded 0, added 0
Progress: resolved 1547, reused 0, downloaded 0, added 0
Progress: resolved 1767, reused 0, downloaded 0, added 0
Progress: resolved 1966, reused 0, downloaded 0, added 0
Progress: resolved 2029, reused 0, downloaded 0, added 0
Progress: resolved 2096, reused 0, downloaded 0, added 0
Progress: resolved 2358, reused 0, downloaded 0, added 0
Progress: resolved 2534, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (2530 entries in 24.8s)
Progress: resolved 2534, reused 0, downloaded 0, added 0, done
[ERR_PNPM_PEER_DEP_ISSUES] Unmet peer dependencies

✕ unmet peer vitest
  Installed: 4.1.11
  Wanted:
    4.1.10:
      @vitest/browser@4.1.10
      @vitest/browser-playwright@4.1.10

✕ unmet peer @vitest/browser-playwright
  Installed: 4.1.10
  Wanted:
    4.1.11:
      vitest@4.1.11
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the renovate/npm-vitest-vulnerability branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack renovate/npm-vitest-vulnerability

bin/jetpack-downloader test jetpack-mu-wpcom-plugin renovate/npm-vitest-vulnerability

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report