https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 10:47:21 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-326964 EUVD-2026-326964 https://cve.radiocsirt.org/vuln/euvd-2026-326964 https://cve.radiocsirt.org/vuln/fkie_cve-2026-47200 <p>Nuxt 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_&lt;routeName&gt; 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.</p> <p>Nuxt 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_&lt;routeName&gt; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-47200 https://cve.radiocsirt.org/vuln/ghsa-hg3f-28rg-4jxj <p><strong>Affected:</strong> npm: nuxt, npm: @nuxt/nitro-server</p> <p>### Summary</p> <p>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_&lt;routeName&gt;` 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.</p> <p>For Nuxt applications that gate a `.server.vue` *page* behind route middleware as their sole auth check, an unauthenticated attacker could bypass that check by requesting `/__nuxt_island/page_&lt;routeName&gt;_&lt;anyhash&gt;` directly and receiving the server-rendered HTML.</p> <p>### Affected configurations</p> <p>All three conditions must hold for an application to be vulnerable:</p> <p>1. `experimental.componentIslands` is enabled (the default in Nuxt 4; opt-in in Nuxt 3). 2. The application defines one or more `.server.vue` files under `pages/`, registering them as routed pages. 3. Authentication / authorization for at least one such page is enforced solely via route middleware (`middleware/*.ts` referenced from `definePageMeta`), without a server-side check inside the page or its data layer.</p> <p>Applications that enforce auth inside the island&#39;s own data layer (server-only API routes, `useRequestEvent` + manual session checks, etc.) were not affected. The general &#34;route middleware does not run for non-page isl…</p> <p><strong>Affected:</strong> npm: nuxt, npm: @nuxt/nitro-server</p> <p>### Summary</p> <p>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_&lt;routeName&gt;` 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.</p> <p>For Nuxt applications that gate a `.server.vue` *page* behind route middleware as their sole auth check, an unauthenticated attacker could bypass that check by requesting `/__nuxt_island/page_&lt;routeName&gt;_&lt;anyhash&gt;` directly and receiving the server-rendered HTML.</p> <p>### Affected configurations</p> <p>All three conditions must hold for an application to be vulnerable:</p> <p>1. `experimental.componentIslands` is enabled (the default in Nuxt 4; opt-in in Nuxt 3). 2. The application defines one or more `.server.vue` files under `pages/`, registering them as routed pages. 3. Authentication / authorization for at least one such page is enforced solely via route middleware (`middleware/*.ts` referenced from `definePageMeta`), without a server-side check inside the page or its data layer.</p> <p>Applications that enforce auth inside the island&#39;s own data layer (server-only API routes, `useRequestEvent` + manual session checks, etc.) were not affected. The general &#34;route middleware does not run for non-page isl…</p> https://cve.radiocsirt.org/vuln/ghsa-hg3f-28rg-4jxj