Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)GHSA-hf59-9xwc-2g4p
LOWFix: nuxt/nuxt@6f1b93cGHSA-hf59-9xwc-2g4p is a low-severity (CVSS 3.1) CWE-116 vulnerability in nuxt. A fix is available for nuxt — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
nuxt📦nuxt📦@nuxt/nitro-server📦@nuxt/nitro-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The fix for CVE-2026-46342 (GHSA-g8wj-3cr3-6w7v) binds each /__nuxt_island/<Name>_<hash>.json path to its props by hashing the (name, props, context, source) tuple. That hash was computed over ohash's serialization, which does not escape quotes inside strings or delimiters inside keys, so two different prop objects can produce the same hash. A request with crafted props can therefore pass validation for another island's path and render different content at that path.
Impact
For example, these two prop objects serialize identically and share one island path:
{ html: '', note: '<img src=x onerror="alert(1)">' }
{ html: '\',note:\'<img src=x onerror="alert(1)">' }
This reopens the scenarios described in GHSA-g8wj-3cr3-6w7v:
nuxt generate/ prerendering. Nuxt caches prerendered island responses by path. If the crawler reaches a link to the colliding URL (for example in user-submitted content included in the build) before it renders the page that uses the legitimate props, the colliding response is written into the generated page.- Path-keyed shared caches. A CDN or reverse proxy that caches
/__nuxt_island/*by path only, ignoring the query, can be primed with the colliding response.
An attacker has to construct props that collide with a specific legitimate tuple, which in practice means at least part of that tuple is a string they control (for example a stored comment or profile field passed as a prop). Where a prop reaches an unsafe HTML sink in the island (v-html, innerHTML, a renderer treating a prop as HTML), the substituted response can execute script in the site's origin. Without such a sink, the impact is content substitution.
Applications are not affected if they do not use server components or <NuxtIsland>, or if no island receives attacker-influenced string props. Server-rendered responses that are not cached by path alone are also unaffected.
Patches
Fixed in [email protected] and @nuxt/[email protected]. The island hash is now computed over a canonical JSON encoding of the tuple, in which strings and keys are escaped, so different props can no longer produce the same hash.
Island hashes change as a result. Clients that build island URLs themselves should use the exported getIslandHash rather than hashing with ohash directly.
Nuxt 3 has reached end of life and will not receive a fix. Upgrade to Nuxt 4.
Workarounds
- Ensure any intermediary cache keys
/__nuxt_island/*on the full query string, not on the path alone. - Treat island props as untrusted input and do not pass them to
v-htmlor other HTML sinks without sanitisation. - When prerendering, avoid including user-submitted links to
/__nuxt_island/in crawled pages, for example by excluding that prefix withnitro.prerender.ignore:
export default defineNuxtConfig({
nitro: {
prerender: {
ignore: [route => route.startsWith('/__nuxt_island/') && route.includes('?')],
},
},
})
Credits
Thanks to rat5ak for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | nuxt | ≥ 4.4.6&&< 4.6.4 | 4.6.4npm install nuxt@4.6.4 |
| 📦npm | nuxt | ≥ 3.21.6 | No fix |
| 📦npm | @nuxt/nitro-server | ≥ 4.4.6&&< 4.6.4 | 4.6.4npm install @nuxt/nitro-server@4.6.4 |
| 📦npm | @nuxt/nitro-server | ≥ 3.21.6 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nuxt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nuxt to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hf59-9xwc-2g4p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-hf59-9xwc-2g4p in your dependencies?
Find it across npm, including transitive dependencies.