nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
4.6.4 is the newest release of 4.x.
Summary· from the note as AI read it
Security fixUpgrade: this release fixes a security issue.
Before you upgrade
- Check code relying on navigateTo returning RouteLocationRaw type.To check
- Check route rules with case-dependent constraints using sensitive: false.To check
Security
- Upgrade to stop dev server reading files named in client error reports.
- Upgrade to block dev server access to nitro dev output.
- Upgrade to prevent generated app secret being served in dev.
- Upgrade to fix dot-segment path handling in request paths.
- Upgrade so redirect route rules apply to page islands.
New
- nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches
- nuxt: server render internal custom links without RouterLink
- nuxt: skip unneeded typed routes generation
In short
2 breaking5 security3 faster16 fixed17 internal
- BreakingTo check
nuxt: hide RouteLocationRaw from navigateTo's public return type
- BreakingTo check
nuxt: reject case-dependent route rule constraints w/
sensitive: false
Security
Fixes 1 advisory that affected 4.6.2
- ModerateNuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routesGHSA-9v7c-q64q-vv33 · 30 Oct 2026Fixed in 4.6.3
5 advisories affect 4.6.3; 4.6.4 fixes the others
- ModerateNuxt exposes the message and data of unhandled errors thrown during server renderingGHSA-96x6-fvhx-49hg · 16 Nov 2026No fix yet
- ModerateNuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesGHSA-f3x9-2chm-73c8 · 16 Nov 2026No fix yet
- ModerateNuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitiveGHSA-vjh5-4x84-xrqp · 22 Oct 2026No fix yet
- LowNuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)GHSA-hf59-9xwc-2g4p · 16 Nov 2026No fix yet
- ModerateNuxt payload URL generation has quadratic cost for repeated slashes in the request pathGHSA-r9jc-w898-3fv6 · 16 Nov 2026Fixed in 4.6.4
Release note
The section about nuxt of a note shared by several packages.
v4.6.3 is the next patch release.
Changelog
Security fixes
- 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
nuxt: apply redirect route rules to page islands (
b20372dbe) - GHSA-2fxj-c3j7-rr69
Performance
nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches
nuxt: server render internal custom links without RouterLink
nuxt: skip unneeded typed routes generation
Fixes
nuxt: defer app scope cleanup on external navigation
nuxt: prevent useCookie CookieStore sync from rewriting with refresh
nuxt: only return redirects from
navigateTowhile middleware runsnuxt: remove purged entries from
_asyncDatanuxt: hide RouteLocationRaw from navigateTo's public return type
nuxt: tree-shake auto-imported
#appcomposablesnuxt: don't treat constrained route rules as covering dynamic pages
nuxt: include
shared/in build cache hashnuxt: hash keyed function ids + page import names relative to
rootDirnuxt: encode page paths before matching route rule keys
nuxt: handle rejected
updateCallbackDoneof aborted view transitionnuxt: reject case-dependent route rule constraints w/
sensitive: falsenuxt: don't case-fold regex constraints in route rule keys
nuxt: normalise page prefix when finding route rule exceptions
nuxt: avoid self-referencing
nuxt/schemaaugmentationnuxt: let nightly runtime resolve its own
nuxt/*importsnuxt: don't warn for vite+
vite.configfilesnuxt: clamp numeric
v-forsources in island renders at render timedeps: update nitropack to 2.13.5 + drop obsolete workarounds
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.