Nuxt: Route middleware not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`
nuxt
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
| @nuxt/nitro-server npm |
|
nuxt
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
| @nuxt/nitro-server npm |
|
3.21.64.4.6Nuxt is an open-source web development framework for Vue.js. In Nuxt versions 3.11.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6 and @nuxt/nitro-server versions 3.20.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6, when experimental.componentIslands is enabled (default in Nuxt 4), any .server.vue file under pages/ is automatically registered as a server island under the key page_<routeName> and exposed via the /__nuxt_island/:name endpoint. Until this fix, requests through that endpoint rendered the page component directly via the SSR renderer without instantiating Vue Router, which meant route middleware declared on the page (including definePageMeta({ middleware })) did not run. This issue has been patched in versions 3.21.6 and 4.4.6.
From the CVE record · GitHub_M
When experimental.componentIslands is enabled (the default in Nuxt 4), .server.vue files under pages/ are exposed through the /__nuxt_island/:name endpoint. Requests to that endpoint render the page without running its route middleware, allowing a remote requester to bypass middleware declared on the page without user interaction.
Check deployments using affected npm nuxt versions >=3.11.0 <3.21.6 or >=4.0.0-alpha.1 <4.4.6, or @nuxt/nitro-server versions >=3.20.0 <3.21.6 or >=4.2.0 <4.4.6.