8000 chore(deps): update pnpm.catalog.default @nuxt/schema to v4.6.4 [security] by renovate[bot] · Pull Request #234 · romhml/compodium · GitHub
[go: up one dir, main page]

Skip to content

chore(deps): update pnpm.catalog.default @nuxt/schema to v4.6.4 [security] - #234

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/npm-nuxt-schema-vulnerability
Nov 16, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/npm-nuxt-schema-vulnerability

Conversation

@renovate
@renovate renovate Bot commented Nov 16, 2026
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@nuxt/schema (source) 4.6.3 → 4.6.4 age confidence

Nuxt dev server serves files from a parent directory with a stray lockfile or workspace file

CVE-2026-128070 / GHSA-mjrq-cffv-q4qc

More information

Details

Summary

Nuxt can pick a parent directory that does not declare a workspace as its default workspaceDir: the farthest directory with a lockfile when the project is not inside a git repository, or the farthest directory with a pnpm-workspace.yaml or deno.json file, even one that only holds settings. The Vite dev server allows /_nuxt/@fs/ requests for any file under workspaceDir. A stray lockfile or settings file in a parent directory, such as the home directory, therefore lets anyone who can reach the dev server read files in that directory and everything below it.

Impact

This affects the development server only; production builds are not affected. All of the following have to hold:

  • A parent directory contains either:
    • a lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock and similar), while the project is not inside a git repository and has no workspace file (pnpm-workspace.yaml, turbo.json, lerna.json and similar) above it. Running npm install once in the home directory is enough to create one there.
    • a pnpm-workspace.yaml without a packages list (for example one that only holds pnpm settings such as onlyBuiltDependencies), or a deno.json or deno.jsonc without a workspace field. This applies even if the project is inside a git repository.
  • The dev server is reachable from the network (nuxt dev --host, nuxt dev --tunnel, a published container port, or a proxy onto the dev port). The default localhost bind limits this to local processes, which can usually read the same files directly.

For example, with ~/package-lock.json and a project at ~/projects/app that has no .git directory, nuxt dev --host serves GET /_nuxt/@fs/<home>/.ssh/id_ed25519 with status 200. Any file in the home directory that is not covered by Vite's server.fs.deny list can be read this way, including SSH keys, cloud credentials and the Nuxt DevTools auth token in ~/.nuxt/devtools/dev-auth-token.txt.

No browser is involved: a plain HTTP client is enough. A web page on another origin cannot read the response, and DNS rebinding is rejected by Vite's host check.

Projects whose parent directories contain none of these files are not affected, nor are projects inside a git repository whose only lockfile is their own. Nuxt 3.5.0 and later are affected.

Patches

Fixed in @nuxt/schema 4.6.4, which nuxt 4.6.4 depends on. A parent directory now only becomes the default workspaceDir if it declares a workspace: a pnpm-workspace.yaml with packages, a deno.json or deno.jsonc with workspace, a lerna.json, turbo.json or rush.json, a package.json with workspaces, or a git repository. A lockfile or a settings file alone no longer widens the dev server's server.fs.allow list. If your monorepo root is not detected this way, set workspaceDir in nuxt.config.ts. Nuxt 3 has reached end of life and will not receive a fix.

Workarounds

Set workspaceDir explicitly in nuxt.config.ts to the project root (or to the real monorepo root), or remove the stray lockfile or settings file from the parent directory. Do not expose the dev server to untrusted networks. If the dev port was reachable from an untrusted network while this layout was in place, treat files in the parent directory as exposed and rotate credentials such as SSH keys and cloud tokens.

Credits

Nuxt thanks @​superboy-zjc for the report.

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

nuxt/nuxt (@​nuxt/schema)

v4.6.4

Compare Source

4.6.4 is a security release. It fixes eight advisories in Nuxt and pulls in nitropack 2.13.6, which fixes three more in Nitro. We recommend upgrading as soon as you can.

⚠️ Behaviour changes

These probably won't affect most apps, but it's worth flagging anyway:

  1. Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with createError. Everything else is stripped.
  2. Dev server Host checks. Webpack and rspack dev servers now reject requests with an unexpected Host header, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the new devServer.allowedHosts option.
  3. workspaceDir detection. When workspaceDir isn't set, Nuxt now only widens it past rootDir to an explicit workspace root or the closest git repository.
  4. Nitropack cached routes. cache, swr and isr route rules now only cache GET and HEAD requests, and no longer store responses that set a cookie or send Cache-Control: private or no-store. Wildcard proxy and redirect rules also reject requests whose resolved target would leave the rule's scope.
  5. Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so /api%2Fadmin is covered by a /api/** rule.

👉 Changelog

compare changes

🩹 Fixes
  • nitro,nuxt: require unrouting 0.3.2 (768d21368)
  • nitro: preserve wildcard tails in case-insensitive route rules (bf31e4cd8)
  • nitro: require nitropack 2.13.6 (1b13c6981)
  • nitro: keep leading double slash in renderer request path (75c12c6fb)
  • nuxt: use unambiguous encoding for island hash (6f1b93c64)
  • vite-server: resolve wildcard redirect tails from the matched segments (1e7dfa6a7)
  • nuxt: do not expose details of untrusted thrown errors (8c56b71e4)
  • nuxt: strip trailing slashes in linear time (97424dd21)
  • nitro,webpack: include hosts the CLI allows after loading the config (8c11d965d)
  • webpack: skip hot middleware for forbidden dev requests (3c9645326)
  • rspack,webpack: reject unexpected Host headers in dev middleware (f8d64c9aa)
  • schema,nitro,vite: add devServer.allowedHosts (3e1c7964e)
  • nitro,nuxt: match route rules for paths with encoded slashes (084396b10)
  • schema: only widen workspace dir to a declared workspace root (89d3306d1)
  • nitro: only trust x-forwarded-proto in when opted-in (#​36818)
  • nitro: stream the body read through a nuxt/server handler (#​36817)
  • kit: suggest the specific fix when loading falls back to jiti (24d75659d)
  • vite: use a single type checker (#​36774)
  • nitro,vite: remove windows + virtual dev ssr css links after hydration (#​36765)
  • nitro,vite: dedupe dev css by module node (#​36420)
  • nuxt: avoid hoisting setup-only values from definePageMeta (#​36751)
  • nuxt: only match hydration modifiers after lazy prefix (#​36750)
  • kit,nitro,nuxt: make emitted tsconfig/types stable across reruns (#​36747)
  • nuxt: render inlined component styles after stylesheet links (#​36714)
  • webpack: use valid devtool for hidden client sourcemaps in dev (#​36555)
📖 Documentation
  • clarify template dependency regeneration (#​36766)
  • revise README structure and headings (#​36772)
  • link the Nuxt DevTools docs on nuxt.com (#​36769)
  • warn against spreading untrusted objects onto server components (1225ca7ff)
  • update anchors for flat heading ids (#​36664)
🏡 Chore
  • add 1000-row listing routes to the benchmark (c852d871f)
  • add client page weight and browser timing suites (#​36788)
✅ Tests
🤖 CI
  • check unversioned docs links against branch docs version (d093c88b1)
  • skip unneeded checks for release prs (4b90681bd)
  • skip benchmarks in merge groups (6428070e0)
  • re-enable codspeed ⚡ (bc17c03d1)
❤️ Contributors

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

@pkg-pr-new
pkg-pr-new Bot commented Nov 16, 2026
Copy link
Copy Markdown
npm i https://pkg.pr.new/romhml/compodium/@compodium/core@234
npm i https://pkg.pr.new/romhml/compodium/@compodium/examples@234
npm i https://pkg.pr.new/romhml/compodium/@compodium/nuxt@234
npm i https://pkg.pr.new/romhml/compodium/@compodium/vue@234

commit: 85acf22

@renovate
renovate Bot merged commit 5bda055 into main Nov 16, 2026
2 checks passed
@renovate
renovate Bot deleted the renovate/npm-nuxt-schema-vulnerability branch November 16, 2026 02:38
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

0