Nuxt island content substitution in path hash generation
nuxt · @nuxt nitro-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
| @nuxt/nitro-server npm |
|
|
Original description
Nuxt is an open-source web development framework for Vue.js. From 3.21.6 to before 4.0.0 and from 4.4.6 until 4.6.4, the /__nuxt_island path hash uses ohash serialization that does not escape quotes in string values or delimiters in object keys, allowing different island-prop tuples to produce the same path. For prerendering, substituted content is written into the generated page only if the crawler reaches a colliding URL before rendering the page with the legitimate props. Separately, a CDN or reverse proxy that keys island responses by path alone can be primed with the colliding response. If the substituted prop reaches v-html, innerHTML, or another unsafe HTML sink, the response can execute script in the application origin; otherwise the impact is content substitution. Applications that do not use server components or NuxtIsland, islands without attacker-influenced string props, and responses not cached by path alone are unaffected. This issue is fixed in version 4.6.4.
From the CVE record · GitHub_M
References
- github.com/nuxt/nuxt/security/advisories/GHSA-hf59-9xwc-2g4p
- github.com/nuxt/nuxt/commit/6f1b93c643355688bc9e2d7434723f7fd3f25092
- github.com/nuxt/nuxt/releases/tag/v4.6.4
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-128076.json
- nvd.nist.gov/vuln/detail/CVE-2026-128076
- github.com/nuxt/nuxt