nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
3.21.11 is the newest release of 3.x.
In short
14 new3 faster26 fixed3 changed41 internal
Security
19 advisories affect 3.14.0; 4.6.2 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
- 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
- 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
14 more
- 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: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcherGHSA-mm7m-92g8-7m47 · 16 Jun 2026Fixed in 3.21.7
- HighNuxt allows DOS via cache poisoning with payload rendering responseGHSA-jvhm-gjrh-3h93 · 19 Mar 2025Fixed in 3.16.0
- ModerateNuxt server islands render `useHeadSafe` input without sanitisationGHSA-xfq5-w38q-pc2x · 22 Oct 2026Fixed in 4.6.2
- ModerateNuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routesGHSA-6gq8-jgmh-3ffp · 22 Oct 2026Fixed in 3.21.4
- 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's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`GHSA-hg3f-28rg-4jxj · 29 May 2026Fixed in 3.21.6
- ModerateNuxt: Reflected XSS in `navigateTo()` external redirectGHSA-fx6j-w5w5-h468 · 19 May 2026Fixed in 3.21.6
- 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.14.0 is the next minor release.
Highlights
Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the unjs side with preparations for Nitro v3!)
Faster starts powered by jiti
Loading the nuxt config file, as well as modules and other build-time code, is now powered by jiti v2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨
Shared folder for code and types shared with client/server
You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.
For this, we have a new shared/ folder (#28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.
If needed you can use the new #shared alias which points to this folder.
The shared folder is alongside your server/ folder. (If you're using compatibilityVersion: 4, this means it's not inside your app/ folder.)
rspack builder
We're excited to announce a new first-class Nuxt builder for rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to use unplugin to make this possible.
Let us know if you like it - and feel free to raise any issues you experience with it.
👉 To try it out, you can use this starter - or just install @nuxt/rspack-builder and set builder: 'rspack' in your nuxt config file.
New composables
We have new useResponseHeader and useRuntimeHook composables (#27131 and #29741).
New module utilities
We now have a new addServerTemplate utility (#29320) for adding virtual files for access inside nitro runtime routes.
v4 changes
We've merged some changes which only take effect with compatibilityVersion: 4, but which you can opt-into earlier.
Previously, if you had a component like
~/components/App/Header.vuethis would be visible in your devtools as<Header>. From v4 we ensure this is<AppHeader>, but it's opt-in to avoid breaking any manual<KeepAlive>you might have implemented. (#28745).Nuxt scans page metadata from your files, before calling
pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before callingpages:extend. Instead, we have a newpages:resolvedhook, which is called afterpages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMetatoafter-resolve, as it solves a number of bugs.
Roadmap to v3.15
They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):
auto-imported directives from modules
'isolated' page renders
Delayed hydration
Upgrading
As usual, our recommendation for upgrading is to run:
npx nuxi@latest 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
deps: Upgrade to latest version of jiti
kit,nuxt,vite,webpack: Reimplement cjs utils using
jitinuxt: Normalise component names to match nuxt pattern
kit,schema: Add
addServerTemplateutilitynuxt: Add
useResponseHeadercomposablerspack,webpack: Add
rspackbuildernuxt,schema:
pages:resolvedhook + scan meta post extendnuxt: Allow enabling route props in
definePageMetaschema,nuxt: Add
shared/folder and#sharedaliasnuxt: Allow chunk error or manifest update -> reload
nuxt: Add
useRuntimeHookcomposable
Performance
nuxt: Remove unneeded second call to
useNuxtAppvite: Avoid redundant postcss plugins overwrite
kit,nuxt,vite,webpack: Hoist regex patterns
Fixes
nuxt: Simplify plugin
InjectionTypetemplate conditionalnuxt: Access server build from
webpackmemfsnuxt: Do not resolve non-absolute component paths
nuxt: Defer unsetting error handler until suspense resolves
nuxt: Pass
DOMExceptionas fetch abort exceptionvite: Don't force protocol if disabled
devServer.httpsnuxt: Empty nitro
buildDirin dev modenuxt: Don't resolve relative import type paths for deps
kit: Handle passing 'bare' relative paths to modules
kit: Try resolving module path from each node_modules dir
kit,vite,webpack: Resolve postcss paths from each modules dir
kit,vite,webpack: Strip
node_modules/from parent urlsnuxt: Add
crossoriginattribute for stylesheetsnuxt: Use
routeRulesto hint pages to prerendernuxt: Pass absolute external link urls to
link:prefetchnuxt: Error on build when required module is missing
nuxt: Prevent 404 when hitting component test endpoint
nuxt: Avoid throwing 404 error before middleware finishes
schema: Use
ConfigLayertype fromc12nuxt: Fix nested page types in
typedPagesnuxt: Allow islands to manipulate head client-side
vite: Dim repeat count in logs
schema: Mark
configFileas required in layer typenuxt: Remove vue compiler hints from auto import
vite: Update signature for
createIsExternalnuxt: Respect existing
propsvalue indefinePageMetaschema: Hoist
nitropack/typesto ensure api routes are typed
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.