CVE-2026-128076: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
Affects nuxtSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 3.1 Low : upgrade to 4.6.4 when convenient.
Data as of 16 Nov 2026, 15:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.1 |
|---|
- Patch
- Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade nuxt and @nuxt/nitro-server to 4.6.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnuxt | Affected
| Fixed in
|
| npmnuxt | Affected
| Fixed in– |
| npm@nuxt/nitro-server | Affected
| Fixed in
|
| npm@nuxt/nitro-server | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Nuxt 4.6.4 and @nuxt/nitro-server 4.6.4 and should be applied. Nuxt 3 users should upgrade to Nuxt 4 as Nuxt 3 is end-of-life and will not be fixed. Until patched, ensure any intermediary caches key `/__nuxt_island/*` URLs by the full query string, not just the path. Avoid passing island props to unsafe HTML sinks like `v-html` without proper sanitization. When prerendering, exclude user-submitted links to `/__nuxt_island/` with query parameters from crawled pages using `nitro.prerender.ignore` configuration.
Description
A flaw in Nuxt's handling of island props hashing allows different prop objects to produce the same hash, causing colliding island paths. This can lead to cached responses being substituted with attacker-controlled content, potentially enabling script execution if unsafe HTML sinks are used. The issue affects Nuxt versions prior to 4.6.4 and certain 3.x versions. A fix is available in Nuxt 4.6.4, which uses canonical JSON encoding to prevent collisions. Workarounds include caching by full query string and sanitizing props before HTML rendering.
References
- github.com/nuxt/nuxt/security/advisories/GHSA-hf59-9xwc-2g4p (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128076 (opens in a new tab)
- github.com/nuxt/nuxt/commit/6f1b93c643355688bc9e2d7434723f7fd3f25092 (opens in a new tab)
- github.com/nuxt/nuxt (opens in a new tab)
- github.com/nuxt/nuxt/releases/tag/v4.6.4 (opens in a new tab)