Authentication Bypass Using an Alternate Path or Channel Affecting nuxt package, versions >=3.11.0 <3.21.6>=4.0.0-alpha.1 <4.4.6
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-NUXT-17111072
- published31 May 2026
- disclosed29 May 2026
- creditrmtsixq
Introduced: 29 May 2026
CVE-2026-47200 (opens in a new tab)How to fix?
Upgrade nuxt to version 3.21.6, 4.4.6 or higher.
Overview
Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel in the route middleware. An attacker can gain unauthorized access to server-rendered page content by directly requesting the /__nuxt_island/page_* endpoint, bypassing authentication or authorization checks enforced solely through route middleware.
Note: This is only exploitable if experimental.componentIslands is enabled, the application defines one or more .server.vue files under pages/, and authentication or authorization for at least one such page is enforced solely via route middleware without a server-side check inside the page or its data layer.
Workaround
This vulnerability can be mitigated by enforcing authentication inside the .server.vue page itself, disabling experimental.componentIslands if not needed, or gating the /__nuxt_island/page_* URL prefix at your reverse proxy or in a server middleware.