Packages

nuxt

4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed

The latest release, 4.6.4, is affected by 4 advisories with no fixed version yet.See advisories
Your version

3.21.10

27 Jul 2026Where it was published

3.21.11 is the newest release of 3.x.

In short

2 security32 fixed6 internal

Security

Release note

⚠️ This is a security release. We recommend upgrading as soon as possible with npx nuxt upgrade --dedupe.

It fixes server-side RCE and unauthorized component instantiation via server island props, a route rule authorization bypass, server component DoS, and dev server path disclosure. Refreshing your lockfile also pulls in @nuxt/devtools@3.3.1, which fixes a separate critical development-only RCE.

If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.

Full details: Nuxt Security Patch Releases and GitHub Security Advisories.

Changelog

compare changes

Fixes

  • nuxt: Clear hide/reset timeouts in set()

  • nuxt: Preserve trailing slash in NuxtLink href when unset

  • vite: Resolve SSR inlined CSS module class name mismatch

  • nuxt: Sync layout meta during middleware on SSR

  • nuxt: Update client URL to match SSR on fatal middleware error

  • nuxt: Watch external component directories in development

  • nuxt: Don't cross-pollute useAsyncData cache on reactive key change

  • nuxt: Return global route for useRoute in detached effect scope

  • nuxt: Ignore custom name or path when reusing an existing page in pages:extend

  • nuxt: Preserve explicit useFetch method inference

  • nuxt: Correct default export detection in plugin metadata

  • nuxt: Reload real page module on HMR of JSX render-function pages

  • vite: Ensure server sourcemap-preserver plugin actually runs

  • nuxt: Resolve @unhead/vue/* from nuxt's dependency tree

  • nuxt: Don't apply scroll behaviour after a subsequent nav

  • vite: Preserve css suffix when extracting ssr inline styles

  • nuxt: Don't exclude client entry module from style extraction

  • kit: Avoid mutating layer configs when resolving options

  • nuxt: Generate layout types even when pages module is disabled

  • nitro: Skip resource hints for stylesheets already rendered as blocking links

  • nuxt: Revalidate cached route payloads instead of using force-cache

  • nuxt: Preserve query params in cached payload extraction

  • rspack,webpack: Resolve loaders and runtime deps from nuxt dirs

  • nuxt: Render client components in nested server components

  • nuxt: Remove dev error overlay when error is cleared

  • rspack,webpack: Resolve bundled postcss defaults from builder

  • schema: Normalise slashes in app.buildAssetsDir

  • nuxt: Case-fold route rule keys to match folded lookups

  • nitro: Require loopback peer for chrome devtools workspace endpoint

  • nitro: Bound island props and v-for to prevent unauthenticated DoS

  • nuxt: Reject reserved template island prop under runtime compiler

  • nuxt: Reject top-level as prop for islands

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.