nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 3.17.4 to 4.6.4
50 releases in betweennotes for 46
Reading releases, release notes and advisories…
Counted from 46 of 50 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking4.6.4
- Breaking4.5.0
- Breaking4.5.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.1.1
- Breaking4.0.0
Security
4 advisories still affect 4.6.4
- Nuxt exposes the message and data of unhandled errors thrown during server renderingmoderate · GHSA-96x6-fvhx-49hg
- Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesmoderate · GHSA-f3x9-2chm-73c8
- Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)low · GHSA-hf59-9xwc-2g4p
- Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitivemoderate · GHSA-vjh5-4x84-xrqp
No published version clears them all yet.
Fixes 15 advisories affecting 3.17.4
- Nuxt: Unauthorized Component Instantiation via Server Island Propsmoderate · GHSA-48hr-524c-v5w3
- Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routesmoderate · GHSA-6gq8-jgmh-3ffp
- Nuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLmoderate · GHSA-934w-87qh-qr26
- Nuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island Propshigh · GHSA-9473-5f9j-94wq
- Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validationhigh · GHSA-9pgf-384g-p7mv
- Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`moderate · GHSA-c9cv-mq2m-ppp3
- Nuxt: Reflected XSS in `navigateTo()` external redirectmoderate · GHSA-fx6j-w5w5-h468
- Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoninglow · GHSA-g8wj-3cr3-6w7v
- Nuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`moderate · GHSA-hg3f-28rg-4jxj
- Nuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island renderinghigh · GHSA-hxcr-hm88-mpq6
- Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledlow · GHSA-jjm6-p2m9-9w4x
- Cross-site scripting via <NoScript> slot content in Nuxt's head componentslow · GHSA-m3q2-p4fw-w38m
- Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcherhigh · GHSA-mm7m-92g8-7m47
- Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revivallow · GHSA-p6jq-8vc4-79f6
- Nuxt server islands render `useHeadSafe` input without sanitisationmoderate · GHSA-xfq5-w38q-pc2x
- 4.6.3
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - 4.6.3
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - 4.6.3
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w - 4.6.3
nitro,nuxt: handle dot segments in request paths (
440250d97) - GHSA-9v7c-q64q-vv33 - 4.6.3
nuxt: apply redirect route rules to page islands (
b20372dbe) - GHSA-2fxj-c3j7-rr69 - 4.6.0
- 4.6.0
- 4.6.0
- 4.5.1
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.
- 4.5.1
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
Release by release
- Breaking
nitro,nuxt: require unrouting 0.3.2
- Fixed
nuxt: use unambiguous encoding for island hash
- Fixed
nuxt: do not expose details of untrusted thrown errors
- Fixed
nuxt: strip trailing slashes in linear time
- Breaking
- Security
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - Security
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - Security
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w - Security
nitro,nuxt: handle dot segments in request paths (
440250d97) - GHSA-9v7c-q64q-vv33
- Security
- Fixed
nuxt: resolve rooted paths through the URL parser
- Fixed
nuxt: resolve empty route types in shared context
- Fixed
nuxt: fix scroll offset for IDs starting with numbers
- Fixed
nuxt: detect vapor slots with
rawVaporSlotKeyfrom vue
- Fixed
- Fixed
nuxt: accept any
baseURLwhen fetch response type is named - Fixed
nuxt: allow
falseinsetPageLayouttypes - Fixed
nuxt: align
Serializeobject types with JSON - Fixed
nuxt: update
publishConfigconfig export extension
- Fixed
- Security
- Security
- Security
- Deprecated
schema: deprecate
nitro.*options duplicated at the top level
- New
nuxt,kit: Skip rewriting unchanged generated files
- New
kit,nuxt: Use lazy imports to improve parsing speed
- New
vite: Skip html entry probes in bare-import resolver
- New
nuxt: Reuse app and component scans for unchanged structures
- New
- Security
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.
- Security
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
- New
nitro: Replace island teleports in a single html pass
- New
nuxt: Add
vue.optionsApiand disable it for v5+
- Security
- Breaking
If you want to test some of the breaking changes of Nuxt v5, you can already opt in with future.compatibilityVersion: 5.
- Breaking
The runtime behaviour is compatible for the vast majority of apps, and promise input (deprecated in v2) is no longer supported.
- New
The dev server now runs in middleware mode via Rsbuild, replacing
webpack-dev-middlewareandwebpack-hot-middleware(#35575). - New
We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).
- Breaking
18 other lines we could not sort, mostly version bumps
- 4.6.4
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. - 4.6.4
Dev server
Hostchecks. Webpack and rspack dev servers now reject requests with an unexpectedHostheader, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the newdevServer.allowedHostsoption. - 4.6.4
workspaceDirdetection. WhenworkspaceDirisn't set, Nuxt now only widens it pastrootDirto an explicit workspace root or the closest git repository. - 4.6.4
Nitropack cached routes.
cache,swrandisrroute rules now only cacheGETandHEADrequests, and no longer store responses that set a cookie or sendCache-Control: privateorno-store. Wildcardproxyandredirectrules also reject requests whose resolved target would leave the rule's scope. - 4.6.4
Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so
/api%2Fadminis covered by a/api/**rule. - 4.6.0
an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
- 4.6.0
the dev server gives you more info, such as why it reloaded or restarted, which
nuxt.configkeys changed, where the time went during a slow start or build, and how long each module took to set up - 4.6.0
it smooths the upgrade to Nuxt 5, which moves to Nitro v3 and h3 v2. Server code written against
nuxt/serveron 4.6 runs unchanged there, so a module can ship one file for both. - 4.6.0
it decouples Nuxt from the Nitro release cycle. Because we 'own' the API, we can adapt to breaking changes in Nitro or h3 without requiring a future major - and we can release Nuxt majors without having to wait for upstream releases.
- 4.6.0
it makes Nuxt's code more maintainable. It helps us preserve the separation of concerns between our API -
/appand/server- and the bundler + server that you ultimately want to build your app.
954 internal lines (docs, tests, tooling) left out.
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.