Skip to content

Update dependency vitest to v4.1.11 [SECURITY] (2.x) - #702

Open
renovate[bot] wants to merge 1 commit into
2.xfrom
renovate/2.x-npm-vitest-vulnerability
Open

renovate[bot] wants to merge 1 commit into
2.xfrom
renovate/2.x-npm-vitest-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 4.1.2 → 4.1.11 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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 OSV and 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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Enabled.

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

@renovate renovate Bot added the renovate label Oct 15, 2026
@renovate

renovate Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
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 warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @studiometa/eslint-plugin-ui@2.0.0-alpha.3
npm error Found: @vitest/coverage-v8@4.1.2
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"4.1.2" from @studiometa/eslint-plugin-ui@2.0.0-alpha.3
npm error   packages/eslint-plugin-ui
npm error     @studiometa/eslint-plugin-ui@2.0.0-alpha.3
npm error     node_modules/@studiometa/eslint-plugin-ui
npm error       workspace packages/eslint-plugin-ui from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @vitest/coverage-v8@"4.1.11" from vitest@4.1.11
npm error node_modules/vitest
npm error   dev vitest@"4.1.11" from @studiometa/eslint-plugin-ui@2.0.0-alpha.3
npm error   packages/eslint-plugin-ui
npm error     @studiometa/eslint-plugin-ui@2.0.0-alpha.3
npm error     node_modules/@studiometa/eslint-plugin-ui
npm error       workspace packages/eslint-plugin-ui from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-11-03T04_15_00_663Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-03T04_15_00_663Z-debug-0.log

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Code Review

Risk: Medium — issues that should be addressed before merge.

Updates the eslint plugin package's direct Vitest development dependency from 4.1.2 to 4.1.11. The lockfile was not regenerated, so the security update is not reproducible through the repository's locked installation.

1 issue found:

  • issue — packages/eslint-plugin-ui/package.json:44 — Regenerate the lockfile for Vitest 4.1.11

Still open from earlier reviews (1 finding):

  • packages/eslint-plugin-ui/package.json:42 — issue: Synchronize the lockfile with the Vitest update

Review usage: 40,457 in (31,116 cached) / 891 out tokens — $0.0040 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit d6c683e.

Previous review runs

Previous run archived 2026-11-03T04:16:06Z

Code Review

Risk: Medium — issues that should be addressed before merge.

This MR updates the eslint plugin package's Vitest development dependency from 4.1.2 to 4.1.11. The corresponding lockfile entry and related Vitest packages remain at their previous versions, and other workspace test dependencies are not updated.

1 issue found:

  • issue — packages/eslint-plugin-ui/package.json:42 — Synchronize the lockfile with the Vitest update

Review usage: 40,709 in (31,328 cached) / 1,062 out tokens — $0.0042 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 16624a4.

Previous run archived 2026-10-28T16:15:57Z

Code Review

Risk: Low — The dependency update is isolated to the ESLint plugin development toolchain and introduces no blocking issues.

Updates the vitest development dependency from 4.1.2 to 4.1.11 in packages/eslint-plugin-ui. The requested Vitest security update is present; no code defects are evident in the diff.


Review usage: 5,954 in (4,434 cached) / 259 out tokens — $0.0008 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.0 for commit ce86c2c.

Previous run archived 2026-10-28T16:04:31Z

Code Review

Risk: Low — The dependency update is isolated to the ESLint plugin package and introduces no blocking issues.

Updates the package's Vitest development dependency from 4.1.2 to 4.1.11 for the stated security fix. No functional source changes are included.


Review usage: 5,949 in (4,428 cached) / 203 out tokens — $0.0007 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.10.3 for commit 74b15aa.

Previous run archived 2026-10-15T19:25:04Z

Code Review

Risk: Low — no blocking issues; safe to merge aside from nits.

Updates the vitest development dependency in @studiometa/eslint-plugin-ui from 4.1.2 to 4.1.11 for the stated security fix. The companion @vitest/coverage-v8 dependency remains at 4.1.2, so the Vitest toolchain is not fully aligned.


Review usage: 8,702 in / 415 out tokens — $0.0027 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.10.3 for commit 2cf00fa.

Previous run archived 2026-10-15T19:15:10Z

Code Review

Risk: Low — The dependency update is narrowly scoped and introduces no demonstrable defects; it is safe to merge.

Updates the vitest development dependency for @studiometa/eslint-plugin-ui from 4.1.2 to 4.1.11 to consume the security fix. No runtime or published-package code is changed.


Review usage: 5,936 in / 245 out tokens — $0.0018 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.10.3 for commit 56c2dc5.

@codecov

codecov Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (2.x@8a3990b). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             2.x     #702   +/-   ##
======================================
  Coverage       ?   86.42%           
  Complexity     ?      145           
======================================
  Files          ?       12           
  Lines          ?      523           
  Branches       ?        0           
======================================
  Hits           ?      452           
  Misses         ?       71           
  Partials       ?        0           
Flag Coverage Δ
unittests 86.42% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate
renovate Bot force-pushed the renovate/2.x-npm-vitest-vulnerability branch 2 times, most recently from 2cf00fa to 74b15aa Compare October 15, 2026 19:24
@renovate
renovate Bot force-pushed the renovate/2.x-npm-vitest-vulnerability branch 2 times, most recently from ce86c2c to 16624a4 Compare October 28, 2026 16:14
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v4.1.11 [security] (2.x) Update dependency vitest to v4.1.11 [SECURITY] (2.x) Oct 28, 2026
@@ -41,7 +41,7 @@
"esbuild": "0.27.4",
"eslint": "9.34.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Synchronize the lockfile with the Vitest update

package-lock.json still records packages/eslint-plugin-ui with vitest at 4.1.2, while this manifest requires 4.1.11. A clean npm ci installation therefore detects an out-of-sync workspace lockfile and fails. Regenerate and commit package-lock.json so it records Vitest 4.1.11 and its resolved dependency tree.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit 16624a4.

@renovate
renovate Bot force-pushed the renovate/2.x-npm-vitest-vulnerability branch from 16624a4 to d6c683e Compare November 3, 2026 04:15
"eslint": "9.34.0",
"typescript": "6.0.2",
"vitest": "4.1.2"
"vitest": "4.1.11"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Regenerate the lockfile for Vitest 4.1.11

package-lock.json still records packages/eslint-plugin-ui with vitest: 4.1.2 and resolves node_modules/vitest plus @vitest/mocker at 4.1.2. A locked install therefore retains the vulnerable version and does not apply the security update. Regenerate and commit package-lock.json so its workspace entry and resolved Vitest tree match 4.1.11.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit d6c683e.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants