chore(deps): update dependency vitest to v4.1.11 [security] #57

renovate-bot · 2026-09-09T05:17:59Z

renovate-bot commented

2026-09-09 05:17:59 +00:00

This PR contains the following updates:

Package	Change	Age	Confidence
vitest (source)	`^4.1.10` → `^4.1.11`
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: 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).

❗ Important

Release Notes retrieval for this PR were skipped because no github.com credentials were available.
If you are self-hosted, please see this instruction.

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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [vitest](https://vitest.dev) ([source](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest)) | [`^4.1.10` → `^4.1.11`](https://renovatebot.com/diffs/npm/vitest/4.1.10/4.1.11) | ![age](https://developer.mend.io/api/mc/badges/age/npm/vitest/4.1.11?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vitest/4.1.10/4.1.11?slim=true) | | [vitest](https://vitest.dev) ([source](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest)) | [`4.1.10` → `4.1.11`](https://renovatebot.com/diffs/npm/vitest/4.1.10/4.1.11) | ![age](https://developer.mend.io/api/mc/badges/age/npm/vitest/4.1.11?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vitest/4.1.10/4.1.11?slim=true) | --- ### Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock [CVE-2026-84373](https://nvd.nist.gov/vuln/detail/CVE-2026-84373) / [GHSA-82fw-gwwq-j7x9](https://github.com/advisories/GHSA-82fw-gwwq-j7x9) <details> <summary>More information</summary> #### 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: ```ts if (mock.type === 'redirect') { return readFile(mock.redirect, 'utf-8') } ``` `mock.redirect` is derived from client input at registration time with no boundary check: ```ts 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 - [https://github.com/vitest-dev/vitest/security/advisories/GHSA-82fw-gwwq-j7x9](https://github.com/vitest-dev/vitest/security/advisories/GHSA-82fw-gwwq-j7x9) - [https://nvd.nist.gov/vuln/detail/CVE-2026-84373](https://nvd.nist.gov/vuln/detail/CVE-2026-84373) - [https://github.com/vitest-dev/vitest/pull/10972](https://github.com/vitest-dev/vitest/pull/10972) - [https://github.com/vitest-dev/vitest/pull/10974](https://github.com/vitest-dev/vitest/pull/10974) - [https://github.com/vitest-dev/vitest/commit/51edf2b072902aec6d30c90ebaafd8f121c6f9d8](https://github.com/vitest-dev/vitest/commit/51edf2b072902aec6d30c90ebaafd8f121c6f9d8) - [https://github.com/vitest-dev/vitest/commit/8ff9b9a9efca7c6cfd5243569440de8d7a33aec4](https://github.com/vitest-dev/vitest/commit/8ff9b9a9efca7c6cfd5243569440de8d7a33aec4) - [https://github.com/vitest-dev/vitest/commit/fe5a11d3ceac5ec10d6d7d21a46d4caca132c48f](https://github.com/vitest-dev/vitest/commit/fe5a11d3ceac5ec10d6d7d21a46d4caca132c48f) - [https://github.com/vitest-dev/vitest](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/v4.1.11) - [https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-rc.2](https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-rc.2) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-82fw-gwwq-j7x9) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> > ❗ **Important** > > Release Notes retrieval for this PR were skipped because no github.com credentials were available. > If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### 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 has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit

2026-09-09 05:18:00 +00:00

chore(deps): update dependency vitest to v4.1.11 [security]

baseline-security / baseline (push) Failing after 1m57s

Details

scan / trivy-fs (push) Failing after 1m25s

Details

baseline-security / baseline (pull_request) Failing after 1m24s

Details

ai-review / review (pull_request) Successful in 3m5s

Details

scan / trivy-fs (pull_request) Failing after 1m2s

Details

0612d837a1

A-Guevara was assigned by renovate-bot

2026-09-09 05:18:04 +00:00

forgejo-actions commented

2026-09-09 05:34:58 +00:00

🔧 Security-gate fix map

The gate failed on these dependency findings — fastest path to green for each:

finding	package	installed → fixed	do this
GHSA-j95f-988m-3j2f (HIGH)	`@tiptap/core`	3.28.0 → 3.30.5	no fix PR yet — `npm update core --package-lock-only`
CVE-2026-84375 (HIGH)	`js-yaml`	4.3.1 → 4.3.2, 3.15.2	no fix PR yet — `npm update js-yaml --package-lock-only`
GHSA-rgj7-g3m4-5g8c (HIGH)	`sharp`	0.35.3 → 0.35.4	no fix PR yet — `npm update sharp --package-lock-only`
CVE-2026-84370 (HIGH)	`svgo`	4.0.2 → 2.8.4, 3.3.5, 4.1.0	no fix PR yet — `npm update svgo --package-lock-only`

⚠ main is itself red right now — this PR likely inherits the backlog rather than adding it. Fixing main (rows above) unblocks every open PR at once.

_{Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.}

### 🔧 Security-gate fix map  The gate failed on these dependency findings — fastest path to green for each: | finding | package | installed → fixed | do this | |---|---|---|---| | GHSA-j95f-988m-3j2f (HIGH) | `@tiptap/core` | 3.28.0 → 3.30.5 | no fix PR yet — `npm update core --package-lock-only` | | CVE-2026-84375 (HIGH) | `js-yaml` | 4.3.1 → 4.3.2, 3.15.2 | no fix PR yet — `npm update js-yaml --package-lock-only` | | GHSA-rgj7-g3m4-5g8c (HIGH) | `sharp` | 0.35.3 → 0.35.4 | no fix PR yet — `npm update sharp --package-lock-only` | | CVE-2026-84370 (HIGH) | `svgo` | 4.0.2 → 2.8.4, 3.3.5, 4.1.0 | no fix PR yet — `npm update svgo --package-lock-only` | > ⚠ `main` is itself red right now — this PR likely **inherits** the backlog rather than adding it. Fixing `main` (rows above) unblocks every open PR at once. Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.

ai-review-bot reviewed

2026-09-09 05:35:24 +00:00

ai-review-bot left a comment

AI review · advisory

Verdict: 1 thing worth fixing (1 medium).

_{⚑ panel: GPT-OSS 120B · Gemma 4 31B · Devstral 2 123B · Laguna S 2.1 — 1 distinct, 1 confirmed, 0 below threshold, 0 refuted · web: not used · context: 2 files under review · 90 codebase · 14 standards chunks (best-grounded: GPT-OSS 120B; smaller windows saw less)}

Panel debate — how this review was reached

Grounding — context: 2 files under review · 90 codebase · 14 standards chunks (best-grounded: GPT-OSS 120B; smaller windows saw less)

Round 1 — independent reviews

GPT-OSS 120B (0 findings, confidence 0.99): No issues detected in the changed lines; version bump and lockfile updates are consistent and safe.
Gemma 4 31B (0 findings, confidence 1.0): The changes are limited to a dependency bump of vitest from v4.1.10 to v4.1.11 and corresponding version updates in package-lock.json and packages/react/package.json, which is correct and consistent.
Devstral 2 123B (1 finding, confidence 0.9): The vitest dependency version in the root package.json should be updated to match the workspace package version to ensure consistency.
Laguna S 2.1 (0 findings, confidence 1.0): The PR correctly updates vitest from 4.1.10 to 4.1.11 across package-lock.json (all @vitest/* packages, internal peer dependency references, and the vitest package itself) and packages/react/package.j

Round 2 — cross-examination

Devstral 2 123B#1 Version mismatch in vitest dependency · confirmed: GPT-OSS 120B, Laguna S 2.1 · refuted: Gemma 4 31B · support 2

Synthesis — Laguna S 2.1 wrote the final review from 1 confirmed finding · promotion: support ≥ 2, and no refutation at high severity.

_{Transcript rv-20260909053347-b4c64a — full round outputs, web results, and model reasoning are viewable by anyone with access to this repository via the AI gateway.}

_{Advisory — never a merge gate. Findings are ordered by how well the panel's own evidence checks out, strongest first. React 👍/👎 on any inline comment to tell it whether it was worth flagging — that is the only feedback this system gets, and every threshold in it is tuned from those reactions. Transcript rv-20260909053347-b4c64a.}

### AI review · advisory  **Verdict: 1 thing worth fixing** (1 medium). ⚑ panel: GPT-OSS 120B · Gemma 4 31B · Devstral 2 123B · Laguna S 2.1 — 1 distinct, 1 confirmed, 0 below threshold, 0 refuted · web: not used · context: 2 files under review · 90 codebase · 14 standards chunks (best-grounded: GPT-OSS 120B; smaller windows saw less) <details> <summary>Panel debate — how this review was reached</summary> **Grounding** — context: 2 files under review · 90 codebase · 14 standards chunks (best-grounded: GPT-OSS 120B; smaller windows saw less) **Round 1 — independent reviews** - **GPT-OSS 120B** (0 findings, confidence 0.99): No issues detected in the changed lines; version bump and lockfile updates are consistent and safe. - **Gemma 4 31B** (0 findings, confidence 1.0): The changes are limited to a dependency bump of vitest from v4.1.10 to v4.1.11 and corresponding version updates in package-lock.json and packages/react/package.json, which is correct and consistent. - **Devstral 2 123B** (1 finding, confidence 0.9): The vitest dependency version in the root package.json should be updated to match the workspace package version to ensure consistency. - **Laguna S 2.1** (0 findings, confidence 1.0): The PR correctly updates vitest from 4.1.10 to 4.1.11 across package-lock.json (all @vitest/* packages, internal peer dependency references, and the vitest package itself) and packages/react/package.j **Round 2 — cross-examination** - `Devstral 2 123B#1` Version mismatch in vitest dependency · confirmed: GPT-OSS 120B, Laguna S 2.1 · refuted: Gemma 4 31B · support 2 **Synthesis** — Laguna S 2.1 wrote the final review from 1 confirmed finding · promotion: support ≥ 2, and no refutation at high severity. Transcript `rv-20260909053347-b4c64a` — full round outputs, web results, and model reasoning are viewable by anyone with access to this repository via the AI gateway. </details> Advisory — never a merge gate. Findings are ordered by how well the panel's own evidence checks out, strongest first. React 👍/👎 on any inline comment to tell it whether it was worth flagging — that is the only feedback this system gets, and every threshold in it is tuned from those reactions. Transcript `rv-20260909053347-b4c64a`.

package-lock.json

					
				@ -23114,7 +23136,7 @@

				    },

package-lock.json:23136 · MEDIUM — Version mismatch in vitest dependency
The root package.json declares vitest ^4.1.10, but the workspace package packages/react/package.json declares ^4.1.11. This inconsistency can lead to different versions being installed across the monorepo, potentially causing compatibility issues.

Fix: Align the vitest version in the root package.json with the workspace package by updating it to ^4.1.11.

Proposed replacement (one-click ⚡ Apply on the findings board at the top of this PR):

"vitest": "^4.1.11"

_{Evidence: partly verified — two or more reviewers, quote or anchor verified (panel 3/4).
👍 if this was worth flagging · 👎 if it was not — a reaction on this comment is the whole feedback loop.}

**`package-lock.json:23136`** · MEDIUM — Version mismatch in vitest dependency The root package.json declares vitest ^4.1.10, but the workspace package packages/react/package.json declares ^4.1.11. This inconsistency can lead to different versions being installed across the monorepo, potentially causing compatibility issues. > **Fix:** Align the vitest version in the root package.json with the workspace package by updating it to ^4.1.11. **Proposed replacement** (one-click ⚡ Apply on the findings board at the top of this PR): ``` "vitest": "^4.1.11" ``` Evidence: **partly verified** — two or more reviewers, quote or anchor verified (panel 3/4). 👍 if this was worth flagging · 👎 if it was not — a reaction on this comment is the whole feedback loop.

renovate-bot force-pushed renovate/npm-vitest-vulnerability from 0612d837a1

baseline-security / baseline (push) Failing after 1m57s

Details

scan / trivy-fs (push) Failing after 1m25s

Details

baseline-security / baseline (pull_request) Failing after 1m24s

Details

ai-review / review (pull_request) Successful in 3m5s

Details

scan / trivy-fs (pull_request) Failing after 1m2s

Details

to a1967cb0bc

ai-review / review (pull_request) Successful in 1m6s

Details

baseline-security / baseline (pull_request) Failing after 1m51s

Details

baseline-security / baseline (push) Failing after 2m1s

Details

scan / trivy-fs (pull_request) Failing after 1m33s

Details

scan / trivy-fs (push) Failing after 1m29s

Details

2026-09-27 23:26:54 +00:00

Compare

forgejo-actions commented

2026-09-28 00:15:57 +00:00

🔧 Security-gate fix map

The gate failed on these dependency findings — fastest path to green for each:

finding	package	installed → fixed	do this
CVE-2026-63671 (HIGH)	`@nuxtjs/mdc`	0.21.1 → 0.22.1	merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f
GHSA-j95f-988m-3j2f (HIGH)	`@tiptap/core`	3.28.0 → 3.30.5	no fix PR yet — `npm update core --package-lock-only`
CVE-2026-84375 (HIGH)	`js-yaml`	4.3.1 → 4.3.2, 3.15.2	no fix PR yet — `npm update js-yaml --package-lock-only`
GHSA-rgj7-g3m4-5g8c (HIGH)	`sharp`	0.35.3 → 0.35.4	no fix PR yet — `npm update sharp --package-lock-only`
CVE-2026-84370 (HIGH)	`svgo`	4.0.2 → 2.8.4, 3.3.5, 4.1.0	no fix PR yet — `npm update svgo --package-lock-only`

⚠ main is itself red right now — this PR likely inherits the backlog rather than adding it. Fixing main (rows above) unblocks every open PR at once.

_{Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.}

### 🔧 Security-gate fix map  The gate failed on these dependency findings — fastest path to green for each: | finding | package | installed → fixed | do this | |---|---|---|---| | CVE-2026-63671 (HIGH) | `@nuxtjs/mdc` | 0.21.1 → 0.22.1 | merge #59 — fix(security): @nuxtjs/mdc ^0.22.2 (CVE-2026-63671) — hold f | | GHSA-j95f-988m-3j2f (HIGH) | `@tiptap/core` | 3.28.0 → 3.30.5 | no fix PR yet — `npm update core --package-lock-only` | | CVE-2026-84375 (HIGH) | `js-yaml` | 4.3.1 → 4.3.2, 3.15.2 | no fix PR yet — `npm update js-yaml --package-lock-only` | | GHSA-rgj7-g3m4-5g8c (HIGH) | `sharp` | 0.35.3 → 0.35.4 | no fix PR yet — `npm update sharp --package-lock-only` | | CVE-2026-84370 (HIGH) | `svgo` | 4.0.2 → 2.8.4, 3.3.5, 4.1.0 | no fix PR yet — `npm update svgo --package-lock-only` | > ⚠ `main` is itself red right now — this PR likely **inherits** the backlog rather than adding it. Fixing `main` (rows above) unblocks every open PR at once. Posted once per head commit by the baseline gate (M2). A Renovate PR that only touches a manifest with no lockfile change is a broken pre-2026-08-06 artifact — check its diff before merging.

ai-review-bot reviewed

2026-09-28 00:16:56 +00:00

ai-review-bot left a comment

AI review · advisory

Verdict: nothing confirmed — 2 single-reviewer observations in the debate digest below.

_{⚑ panel: Gemma 4 31B · Laguna S 2.1 (no review: GPT-OSS 120B, Devstral 2 123B) — 2 distinct, 0 confirmed, 2 below threshold, 0 refuted · web: not used · context: 2 files under review · 90 codebase · 6 standards chunks}

Panel debate — how this review was reached

Grounding — context: 2 files under review · 90 codebase · 6 standards chunks

Round 1 — independent reviews

Gemma 4 31B (0 findings, confidence 1.0 · thought 3.0k + wrote 83 of 16.0k tokens · 78 s): The changes are a standard security update for vitest and a consistent project version bump across the monorepo; the lockfile additions for cac and commander are expected side effects of the environme
Laguna S 2.1 (2 findings, confidence 0.45 · wrote 597 of 65.5k tokens · 7 s): The PR bumps vitest to 4.1.11 and updates package-lock.json accordingly, but leaves the root package.json devDependency at ^4.1.10, so the lockfile's root packages entry is inconsistent with the state
GPT-OSS 120B — no review: the call failed.
Devstral 2 123B — no review: the call failed.

Round 2 — cross-examination

Laguna S 2.1#1 Root package.json vitest range lags the lockfile bump · confirmed: Gemma 4 31B · refuted: — · support 1
Laguna S 2.1#2 packages/react lockfile devDependency pinned but root not advanced · confirmed: Gemma 4 31B · refuted: — · support 1

Not posted (support < 2, or contested at a severity where one refutation vetoes)

Laguna S 2.1#1 Root package.json vitest range lags the lockfile bump (support 1)
Laguna S 2.1#2 packages/react lockfile devDependency pinned but root not advanced (support 1)

Synthesis — Laguna S 2.1 wrote the final review from 0 confirmed findings (+2 below threshold) · promotion: support ≥ 2, and no refutation at high severity.

_{Transcript rv-20260928001438-c53ee0 — full round outputs, web results, and model reasoning are viewable by anyone with access to this repository via the AI gateway.}

_{Advisory — never a merge gate. Findings are ordered by how well the panel's own evidence checks out, strongest first. React 👍/👎 on any inline comment to tell it whether it was worth flagging — that is the only feedback this system gets, and every threshold in it is tuned from those reactions. Transcript rv-20260928001438-c53ee0.}

### AI review · advisory  **Verdict: nothing confirmed** — 2 single-reviewer observations in the debate digest below. ⚑ panel: Gemma 4 31B · Laguna S 2.1 (no review: GPT-OSS 120B, Devstral 2 123B) — 2 distinct, 0 confirmed, 2 below threshold, 0 refuted · web: not used · context: 2 files under review · 90 codebase · 6 standards chunks <details> <summary>Panel debate — how this review was reached</summary> **Grounding** — context: 2 files under review · 90 codebase · 6 standards chunks **Round 1 — independent reviews** - **Gemma 4 31B** (0 findings, confidence 1.0 · thought 3.0k + wrote 83 of 16.0k tokens · 78 s): The changes are a standard security update for vitest and a consistent project version bump across the monorepo; the lockfile additions for cac and commander are expected side effects of the environme - **Laguna S 2.1** (2 findings, confidence 0.45 · wrote 597 of 65.5k tokens · 7 s): The PR bumps vitest to 4.1.11 and updates package-lock.json accordingly, but leaves the root package.json devDependency at ^4.1.10, so the lockfile's root packages entry is inconsistent with the state - **GPT-OSS 120B** — no review: the call failed. - **Devstral 2 123B** — no review: the call failed. **Round 2 — cross-examination** - `Laguna S 2.1#1` Root package.json vitest range lags the lockfile bump · confirmed: Gemma 4 31B · refuted: — · support 1 - `Laguna S 2.1#2` packages/react lockfile devDependency pinned but root not advanced · confirmed: Gemma 4 31B · refuted: — · support 1 **Not posted** (support < 2, or contested at a severity where one refutation vetoes) - `Laguna S 2.1#1` Root package.json vitest range lags the lockfile bump (support 1) - `Laguna S 2.1#2` packages/react lockfile devDependency pinned but root not advanced (support 1) **Synthesis** — Laguna S 2.1 wrote the final review from 0 confirmed findings (+2 below threshold) · promotion: support ≥ 2, and no refutation at high severity. Transcript `rv-20260928001438-c53ee0` — full round outputs, web results, and model reasoning are viewable by anyone with access to this repository via the AI gateway. </details> Advisory — never a merge gate. Findings are ordered by how well the panel's own evidence checks out, strongest first. React 👍/👎 on any inline comment to tell it whether it was worth flagging — that is the only feedback this system gets, and every threshold in it is tuned from those reactions. Transcript `rv-20260928001438-c53ee0`.

ai-review / review (pull_request) Successful in 1m6s

Details

baseline-security / baseline (pull_request) Failing after 1m51s

Required

Details

baseline-security / baseline (push) Failing after 2m1s

Details

scan / trivy-fs (pull_request) Failing after 1m33s

Details

scan / trivy-fs (push) Failing after 1m29s

Details

This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/npm-vitest-vulnerability:renovate/npm-vitest-vulnerability

git switch renovate/npm-vitest-vulnerability

Sign in to join this conversation.

No reviewers

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

tti/tti-ux!57

				`@ -23114,7 +23136,7 @@`
				`},`

Rows
Columns

chore(deps): update dependency vitest to v4.1.11 [security] #57

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

Details

Summary

Affected code

Registration paths and trust boundaries

Path handling

Scope / preconditions

Impact

Affected versions

Fix

Severity

References

Configuration

🔧 Security-gate fix map

AI review · advisory

🔧 Security-gate fix map

AI review · advisory

Checkout

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