nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
3.21.11 is the newest release of 3.x.
In short
25 new4 faster27 fixed2 changed35 internal
Security
17 advisories affect 3.6.0; 4.6.0 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
- CriticalNuxt vulnerable to remote code execution via the browser when running the test locallyGHSA-v784-fjjh-f8r4 · 5 Aug 2024Fixed in 3.12.4
- HighNuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validationGHSA-9pgf-384g-p7mv · 5 Aug 2026Fixed in 3.21.10
12 more
- HighNuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island PropsGHSA-9473-5f9j-94wq · 5 Aug 2026Fixed in 3.21.10
- HighNuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island renderingGHSA-hxcr-hm88-mpq6 · 5 Aug 2026Fixed in 3.21.10
- HighNuxt allows DOS via cache poisoning with payload rendering responseGHSA-jvhm-gjrh-3h93 · 19 Mar 2025Fixed in 3.16.0
- ModerateNuxt: Unauthorized Component Instantiation via Server Island PropsGHSA-48hr-524c-v5w3 · 5 Aug 2026Fixed in 3.21.10
- ModerateNuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLGHSA-934w-87qh-qr26 · 16 Jun 2026Fixed in 3.21.7
- ModerateNuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`GHSA-c9cv-mq2m-ppp3 · 16 Jun 2026Fixed in 3.21.7
- ModerateNuxt: Reflected XSS in `navigateTo()` external redirectGHSA-fx6j-w5w5-h468 · 19 May 2026Fixed in 3.21.6
- Moderatenuxt vulnerable to Cross-site Scripting in navigateTo if used after SSRGHSA-vf6r-87q4-2vjf · 5 Aug 2024Fixed in 3.12.4
- LowNuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledGHSA-jjm6-p2m9-9w4x · 22 Oct 2026Fixed in 4.6.0
- LowCross-site scripting via <NoScript> slot content in Nuxt's head componentsGHSA-m3q2-p4fw-w38m · 16 Jun 2026Fixed in 3.21.7
- LowNuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoningGHSA-g8wj-3cr3-6w7v · 19 May 2026Fixed in 3.21.6
- LowNuxt has Client-Side Path Traversal in Nuxt Island Payload RevivalGHSA-p6jq-8vc4-79f6 · 17 Sep 2025Fixed in 3.19.0
Release note
3.6.0 is the next minor release, packed with improvements and bug fixes.
Upcoming news
In the coming week you can expect two announcements:
The open-sourcing of
nuxt/cliby @pi0 - a new, drop-in replacement fornuxifeaturing more extensibility and better DX. We are aiming to release this alongside Nuxt 3.7, but you would be very welcome to test and contribute tonuxi-ngbefore then!Three significant RFCs: Nuxt Font, Nuxt Assets and Nuxt Scripts. We're expecting an initial POC to take shape in the next month, and would very much appreciate community feedback on this.
Highlights
This minor release contains quite a lot, and we have big plans
SPA loading indicator
If your site is served with ssr: false or you have disabled server-rendering on some of your pages, you might be particularly interested in the new built-in SPA loading indicator.
You can now place an HTML file in ~/app/spa-loading-template.html with some HTML you would like to use to render a loading screen that will be rendered until your app is hydrated on these pages.
👉 By default an animated Nuxt icon is rendered. You can completely disable this indicator by setting spaLoadingTemplate: false in your nuxt configuration file.
Performance improvements
The first thing that happens when your app is hydrated is that your plugins run, and so we now perform build-time optimisations on your plugins, meaning they do not need to be normalised or reordered at runtime.
We also include your error component JS in your main entrypoint, meaning that if an error occurs when a user has no connectivity, you can still handle it with your ~/error.vue. (This also should decrease your total bundle size.)
👉 Compared to Nuxt 3.5.3, the minimal client bundle has decreased by ~0.7kB. Let's keep this up!
Fully static server components
It has been possible to use server components on static pages, but until now they would increase the payload size of your application. That is no longer true. We now store rendered server components as separate files, which are preloaded before navigation.
👉 This does rely on the new, richer JSON payload format, so make sure you have not disabled this by setting experimental.renderJsonPayloads to false.
Better style inlining
If you're monitoring your metrics closely and have not turned off experimental.inlineSSRStyles, you should see more CSS inlined in your page, and a significantly external CSS file. We're now better at deduplicating global CSS, particularly added by libraries like tailwind or unocss.
Animation controls
To give you more fine-grained control over your page/layout components, for example to create custom transitions with GSAP or other libraries, we now allow you to set pageRef on <NuxtPage> and layoutRef on <NuxtLayout. These will get passed through to the underlying DOM elements.
Automatic 'static' preset detection
Up to now, running nuxt generate produced the same output on every deployment provider, but with Nuxt 3.6 we now enable static provider presets automatically. That means if you are deploying a static build (produced with nuxt generate) to a supported provider (currently vercel and netlify with cloudflare and github pages coming soon) we'll prerender your pages with special support for that provider.
This means we can configure any route rules (redirects/headers/etc) that do not require a server function. So you should get the best of both worlds when deploying a site that doesn't require runtime SSR. It also unblocks use of Nuxt Image on Vercel (with more potential for automatic provider integration coming soon).
Increased type safety
We now have better support for server-specific #imports and augmentations if you are using the new ~/server/tsconfig.json we shipped in Nuxt 3.5. So when importing from #imports in your server directory, you'll get IDE auto-completion for the right import locations in Nitro, and won't see Vue auto-imports like useFetch that are unavailable within your server routes.
You should now also have type support for runtime Nitro hooks.
Finally, we have removed more locations where objects had a default any type. This should improve type safety within Nuxt in a number of locations where unspecified types fell back to any:
RuntimeConfigPageMetaNuxtApp['payload'](accessible now fromNuxtPayloadinterface)ModuleMeta
You can find out more about how to update your code if this affects you in the original PR.
Nitro 2.5 built-in
This release ships with new Nitro 2.5, which has a whole list of exciting improvements that are worth checking out.
Of particular note is experimental support for streaming, which is also enabled by a couple of changes in Nuxt itself.
New tools for module authors
This release brings a number of utilities for modules authors to easily add type templates and assert compatibility with a given version of another module.
In addition, this release will finally unlock a new nuxt/module-builder mode that should improve type support for module authors. If you're a module author, you might consider following these migration steps to try it out in the coming days.
Upgrading
As usual, our recommendation for upgrading is to run:
nuxi upgrade --force
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
Enhancements
nuxt: Sync
useCookiestate between tabskit: Module compatibility utils
nuxt: Add
renderResulttoapp:renderedwebpack: Allow configuring
esbuild-loaderoptionsnuxt: Add
openoption innavigateTohelperwebpack, schema: Add webpack experiments configuration
nuxt: Provide
clearNuxtStatecomposablekit:
addTypeTemplatehelper with auto-registrationnuxt: Return
statusfromuseAsyncDatanuxt: Allow accessing
NuxtPageref viapageRefnuxt: Allow accessing
NuxtLayoutref vialayoutRefnuxt: Emit error in
ssr-erroreventnuxt: Start loading indicator state with middleware
kit: Allow direct function in
defineNuxtModulenuxt: Expose
useNuxtAppto window for conveniencenuxt: Allow configuring spa loading indicator
nuxt: Add types for nuxt-defined nitro runtime hooks
Performance
nuxt: Mark define functions as side-effect free at source
nuxt: Import error component synchronously
nuxt: Use prerendered islands to serialise/revive payload
nuxt: Extract and apply plugin order at build time
Fixes
nuxt: Handle page rendering on different path
nuxt: Replace BigInt literal with BigInt constructor
vite: Remove
resolveIdworkaround and update vite-nodeschema: Remove obsolete terser option from webpack config
nuxt: Skip vue render when redirecting
nuxt: Avoid early returning renderer with empty response
nuxt: Add missing vue types
nuxt: Prefix server component ids to avoid collisions
schema: Add more explicit types for config schema
nuxi,nuxt: Remove baseUrl + use relative paths in tsconfig
vite: Invalidate templates by
dstnotsrcnuxt: Don't disable vue endpoint in dev mode
nuxt: Respect query/hash for external routes in
navigateTonuxt: Abort navigation when updating
window.locationvite: Ignore and warn if vite config file exists
nuxt: Ensure prerendered components are treated as islands
nuxt: Improve warning for invalid children of
<Title>nuxt: Replace
:in rendered server components (for win)cli: Add back default
baseUrlintsconfig.jsonnuxt: Post non-proxied cookie value via
BroadcastChannelnuxt: Stop indicator when not changing page component
nuxt: Scroll to top in nested routes
nuxt: Inline css directly in root component
nuxt: Move to
@typescript-eslint/typescript-estreenuxt: Guard
res.end()calls with check if event is handlednuxt: Do not embed error path in payload
nuxt: Use static nitro build if possible
nuxt: Add aliases and augmentations for nitro context
nuxt,schema: Prefer unknown rather than any for signatures
schema: Change
redirecttype forNuxtPagetypenuxt: Fix error on layout switching
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.