Skip to content

chore(deps): update dependency vitest to v5 [security] - #775

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 Sep 10, 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.0.0 → ^5.0.0 age confidence
vitest (source) ^3.1.4 → ^5.0.0 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)

v5.0.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes
   🚀 Features

[!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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 requested a review from a team as a code owner September 10, 2026 00:31
@renovate renovate Bot added the javascript label Sep 10, 2026
@renovate

renovate Bot commented Sep 10, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @netlify/ai@1.0.2
npm error Found: @types/node@20.14.15
npm error node_modules/@types/node
npm error   dev @types/node@"20.14.15" from @netlify/ai@1.0.2
npm error   packages/ai
npm error     @netlify/ai@1.0.2
npm error     node_modules/@netlify/ai
npm error       workspace packages/ai from the root project
npm error       1 more (@netlify/dev)
npm error   @types/node@">=20.0.0" from happy-dom@21.0.4
npm error   node_modules/happy-dom
npm error     peerOptional happy-dom@"*" from vitest@5.0.5
npm error     node_modules/vitest
npm error       dev vitest@"^5.0.0" from @netlify/ai@1.0.2
npm error       packages/ai
npm error         @netlify/ai@1.0.2
npm error         node_modules/@netlify/ai
npm error       7 more (@vitest/browser-playwright, @vitest/browser-preview, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional @types/node@"^20.19.0 || >=22.12.0" from vite@8.3.5
npm error node_modules/vite
npm error   peer vite@"^6.4.0 || ^7.0.0 || ^8.0.0" from vitest@5.0.5
npm error   node_modules/vitest
npm error     dev vitest@"^5.0.0" from @netlify/ai@1.0.2
npm error     packages/ai
npm error       @netlify/ai@1.0.2
npm error       node_modules/@netlify/ai
npm error     7 more (@vitest/browser-playwright, @vitest/browser-preview, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-22T19_06_33_366Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-22T19_06_33_366Z-debug-0.log

@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f4c7f85d-20eb-47be-9c44-335cbda313b5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a5fe858 to 1dd3b14 Compare September 10, 2026 15:18
@renovate
renovate Bot requested a review from a team as a code owner September 10, 2026 15:18
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 10, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1dd3b14 to 1972bb2 Compare September 10, 2026 16:58
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 10, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 1972bb2 to a81f6fa Compare September 11, 2026 14:22
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a81f6fa to e156829 Compare September 11, 2026 14:24
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e156829 to d17369a Compare September 11, 2026 14:36
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d17369a to f437b18 Compare September 11, 2026 14:39
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f437b18 to 7e0e6b7 Compare September 11, 2026 14:49
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 7e0e6b7 to 11a753a Compare September 11, 2026 14:51
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 11a753a to 65bb3b8 Compare September 14, 2026 11:13
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 14, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 65bb3b8 to c863ff2 Compare September 14, 2026 11:15
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 14, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from c863ff2 to ce98c80 Compare September 14, 2026 11:23
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 14, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from ce98c80 to 403a572 Compare September 14, 2026 11:25
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 14, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3491e24 to 2c0043f Compare September 16, 2026 20:38
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 16, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 2c0043f to 3444302 Compare September 17, 2026 04:48
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 17, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 3444302 to f53caab Compare September 17, 2026 22:37
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 17, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f53caab to 8f4264f Compare September 18, 2026 04:26
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 18, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 8f4264f to 347ab1e Compare September 19, 2026 00:10
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 19, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 347ab1e to 04a89fc Compare September 19, 2026 03:55
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 19, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 04a89fc to 1c851e0 Compare September 24, 2026 04:12
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 24, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch 2 times, most recently from 3d91558 to 9af8fa6 Compare September 25, 2026 05:37
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 25, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 9af8fa6 to a907c36 Compare September 30, 2026 07:56
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from a907c36 to d90a688 Compare September 30, 2026 07:58
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from d90a688 to 0f4b0ca Compare September 30, 2026 08:30
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from 0f4b0ca to e45c7af Compare September 30, 2026 08:34
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from e45c7af to f2fb5ca Compare September 30, 2026 08:44
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4 [security] chore(deps): update dependency vitest to v5 [security] Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vitest-vulnerability branch from f2fb5ca to e9d887e Compare September 30, 2026 14:23
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 [security] chore(deps): update dependency vitest to v4 [security] Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants