---
title: "GHSA-hf59-9xwc-2g4p: Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)"
description: "Low severity. Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342). Affects @nuxt/nitro-server, nuxt."
url: https://inlinr.com/advisories/GHSA-hf59-9xwc-2g4p
lang: en
---

[Packages](https://inlinr.com/packages)

Low Vulnerability GHSA-hf59-9xwc-2g4p CVE-2026-128076 Published 16 Nov 2026

# Nuxt: Colliding island props can share one \`/\_\_nuxt\_island\` path (incomplete fix for CVE-2026-46342)

Your version of @nuxt/nitro-server 

Affected releases · [@nuxt/nitro-server](https://inlinr.com/packages/@nuxt/nitro-server)

- 4.x 4.2.0 – 4.6.4 No fix on this line yet
- 3.x 3.21.6 – 3.21.11 No fix on this line yet

No release fixes it yet, not even the latest, 4.6.4.

Every release on a timeline

4.x 

1. Affected

4.2.0 – 4.6.4  
19 releases, latest

3.x 

1. Not affected

3.20.0 – 3.21.5  
8 releases
2. Affected

3.21.6 – 3.21.11  
6 releases

34 stable releases of @nuxt/nitro-server, oldest to newest, one row per major.

Your version of nuxt 

Affected releases · [nuxt](https://inlinr.com/packages/nuxt)

- 4.x 4.0.0 – 4.6.4 No fix on this line yet
- 3.x 3.21.6 – 3.21.11 No fix on this line yet

No release fixes it yet, not even the latest, 4.6.4.

Every release on a timeline

4.x 

1. Affected

4.0.0 – 4.6.4  
27 releases, latest

3.x 

1. Not affected

3.0.0 – 3.21.5  
86 releases
2. Affected

3.21.6 – 3.21.11  
6 releases

282 stable releases of nuxt, oldest to newest, one row per major.

## What happens

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 `nuxt@4.6.4` and `@nuxt/nitro-server@4.6.4`. 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-html` or other HTML sinks without sanitisation.
- When prerendering, avoid including user-submitted links to `/__nuxt_island/` in crawled pages, for example by excluding that prefix with `nitro.prerender.ignore`:

```
export default defineNuxtConfig({
  nitro: {
    prerender: {
      ignore: [route => route.startsWith('/__nuxt_island/') && route.includes('?')],
    },
  },
})
```

Credits

Thanks to rat5ak for reporting this issue.

## How it is exploited

Exploitable over the network, with no account and a user to do something.

- **Confidentiality**: none
- **Integrity**: low
- **Availability**: none

CVSS:3.1/​AV:N/​AC:H/​PR:N/​UI:R/​S:U/​C:N/​I:L/​A:N

## References

- [Reference](https://github.com/nuxt/nuxt/security/advisories/GHSA-hf59-9xwc-2g4p "https://github.com/nuxt/nuxt/security/advisories/GHSA-hf59-9xwc-2g4p")  
github.com/nuxt/nuxt/security/advisories/GHSA-h…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-128076 "https://nvd.nist.gov/vuln/detail/CVE-2026-128076")  
nvd.nist.gov/vuln/detail/CVE-2026-128076
- [Fix commit](https://github.com/nuxt/nuxt/commit/6f1b93c643355688bc9e2d7434723f7fd3f25092 "https://github.com/nuxt/nuxt/commit/6f1b93c643355688bc9e2d7434723f7fd3f25092")  
6f1b93c
- [Package](https://github.com/nuxt/nuxt "https://github.com/nuxt/nuxt")  
github.com/nuxt/nuxt
- [Reference](https://github.com/nuxt/nuxt/releases/tag/v4.6.4 "https://github.com/nuxt/nuxt/releases/tag/v4.6.4")  
github.com/nuxt/nuxt/releases/tag/v4.6.4

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
