Skip to content

chore(deps): update dependency vitest to v4 [security] - #6387

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 26, 2026 •

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) 3.2.6 → 4.1.11 age confidence

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: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

References

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


Release Notes

vitest-dev/vitest (vitest)

v4.1.11

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.10

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.9

Compare Source

🐞 Bug Fixes
  • Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in #​10546 (a5180)
  • browser:
    • Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in #​10555 (7fb29)
    • Wait for iframe tester readiness before preparing [backport to v4] - by Vladimir and Séamus O'Connor in #​10497 and #​10556 (fbc62)
  • mocker:
    • Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in #​10548 (2c955)
  • pool:
    • Prevent test run hang on worker crash [backport to v4] - by Ari Perkkiö and Jattioui Ismail in #​10543 and #​10564 (934b0)
View changes on GitHub

v4.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.6

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.4

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.3

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.2

Compare Source

This release bumps Vitest's flatted version and removes version pinning to resolve flatted's CVE related issues (#​9975).

   🐞 Bug Fixes
    View changes on GitHub

v4.1.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes

[!IMPORTANT]
✂ 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 is behind base branch, 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.

@alwaysmeticulous

alwaysmeticulous Bot commented Jul 26, 2026 •

Copy link
Copy Markdown

✅ Meticulous spotted 0 visual differences across 290 screens tested: view results.

Meticulous evaluated ~4 hours of user flows against your PR.

Expected differences? Click here. Last updated for commit 4aaabf2 chore(deps): update dependency vitest to v3 [security]. This comment will update as new commits are pushed.

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c28617d to e2c9dc2 Compare July 26, 2026 05:18
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e2c9dc2 to b87a93d Compare July 26, 2026 08:46
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b87a93d to 0472d22 Compare July 26, 2026 12:51
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0472d22 to 35d9a42 Compare July 26, 2026 18:23
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 35d9a42 to 95ce619 Compare July 26, 2026 20:44
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 95ce619 to c6a61c3 Compare July 27, 2026 00:47
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c6a61c3 to 0e011cf Compare July 27, 2026 04:50
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0e011cf to 806f9ae Compare July 27, 2026 10:22
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 806f9ae to d6aea2b Compare July 27, 2026 13:14
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d6aea2b to 348319e Compare July 27, 2026 18:14
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 348319e to ba3aefd Compare July 27, 2026 23:05
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ba3aefd to cbadd61 Compare August 10, 2026 22:58
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from cbadd61 to b98ad5f Compare August 11, 2026 01:04
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from b98ad5f to 71af27a Compare August 25, 2026 14:20
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 4aaabf2 to 877d82b Compare October 25, 2026 02:37
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v3 [security] chore(deps): update dependency vitest to v4 [security] Oct 25, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 877d82b to 3931c6f Compare October 25, 2026 04:43
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3931c6f to 6a5c0cf Compare October 25, 2026 10:12
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 6a5c0cf to a3c3cbb Compare October 25, 2026 12:37
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a3c3cbb to f7faeef Compare October 25, 2026 17:21
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f7faeef to de0959a Compare October 25, 2026 22:00
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from de0959a to 1240eee Compare October 26, 2026 02:16
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1240eee to eaf7c77 Compare October 26, 2026 06:18
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from eaf7c77 to 274a85d Compare October 26, 2026 08:38
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 274a85d to cca78ac Compare October 26, 2026 13:11
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from cca78ac to 84283e3 Compare October 26, 2026 23:47
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 84283e3 to a27e765 Compare October 27, 2026 03:10
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a27e765 to f701e86 Compare October 27, 2026 06:23
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f701e86 to f0b913b Compare October 27, 2026 09:46

This branch had an error being deployed

1 failed deployment
Preview – parca-ui — a32d02e5 Deployed Oct 30, 2026 by vercel[bot]
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