LowGHSA-hf59-9xwc-2g4pCVE-2026-128076

Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)

Published 16 Nov 2026 · Updated 16 Nov 2026

Is your project on an affected nuxt?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

nuxtnpm
Affected
>=4.4.6 <4.6.4
Fixed in
4.6.4
Update to the fixed version for your release line, for example:npm install nuxt@4.6.4
nuxtnpm
Affected
>=3.21.6
Fixed in
No fix released
Affected
>=4.4.6 <4.6.4
Fixed in
4.6.4
Update to the fixed version for your release line, for example:npm install @nuxt/nitro-server@4.6.4
Affected
>=3.21.6
Fixed in
No fix released

Details

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.

Is GHSA-hf59-9xwc-2g4p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected nuxt, and gives you the command that fixes it.

More advisories for nuxt

  • MediumCVE-2026-128075Nuxt exposes the message and data of unhandled errors thrown during server rendering · 16 Nov 2026
  • MediumCVE-2026-128074Nuxt payload URL generation has quadratic cost for repeated slashes in the request path · 16 Nov 2026
  • MediumCVE-2026-128071Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes · 16 Nov 2026
  • MediumCVE-2026-119200Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes · 30 Oct 2026
  • MediumCVE-2026-114132Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive · 22 Oct 2026
  • MediumCVE-2026-114133Nuxt server islands render `useHeadSafe` input without sanitisation · 22 Oct 2026
All 30 advisories for nuxt

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.