Read the docs

Colliding island props can share one path in Nuxt

Priority LOW 14CWE-116Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

Nuxt from 3.21.6 before 4.0.0 and from 4.4.6 before 4.6.4 is affected, including the nuxt and @nuxt/nitro-server packages. The /__nuxt_island path hash does not escape quotes or delimiters (CWE-116), so different island props can produce the same path. An attacker can substitute content in prerendered pages or poison a CDN or reverse proxy that caches responses by path alone. If the substituted prop reaches an unsafe HTML sink, the attacker can run script in the application origin.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

EPSS 0.00116 1st percentileScored 2026-11-16
Fix Fixed nuxt (nuxt): 4.0.0, 4.6.4nitro-server (@nuxt): 4.0.0, 4.6.4+2 more products

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
nuxtnuxt3.21.6 to before 4.0.0; 4.4.6 to before 4.6.44.0.0, 4.6.4Patch availableCNA
nuxtnitro-server3.21.6 to before 4.0.0; 4.4.6 to before 4.6.44.0.0, 4.6.4Patch availableCNA
—nuxt (npm)4.4.6 to before 4.6.44.6.4Patch availableGHSA-hf59-9xwc-2g4p
—nuxt (npm)3.21.6 and later—No fix listedGHSA-hf59-9xwc-2g4p
—@nuxt/nitro-server (npm)4.4.6 to before 4.6.44.6.4Patch availableGHSA-hf59-9xwc-2g4p
—@nuxt/nitro-server (npm)3.21.6 and later—No fix listedGHSA-hf59-9xwc-2g4p
  • nuxt Vendornuxt Affected 3.21.6 to before 4.0.0; 4.4.6 to before 4.6.4 Fixed in 4.0.0, 4.6.4 Patch available CNA
  • nitro-server Vendornuxt Affected 3.21.6 to before 4.0.0; 4.4.6 to before 4.6.4 Fixed in 4.0.0, 4.6.4 Patch available CNA
  • nuxt (npm) Vendor— Affected 4.4.6 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-hf59-9xwc-2g4p
  • nuxt (npm) Vendor— Affected 3.21.6 and later Fixed in — No fix listed GHSA-hf59-9xwc-2g4p
  • @nuxt/nitro-server (npm) Vendor— Affected 4.4.6 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-hf59-9xwc-2g4p
  • @nuxt/nitro-server (npm) Vendor— Affected 3.21.6 and later Fixed in — No fix listed GHSA-hf59-9xwc-2g4p

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:*——nuxt
  • cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:* Versions — — ·nuxt

Remediation

Upgrade nuxt and @nuxt/nitro-server to 4.0.0 or 4.6.4. The sources list no fixed version for nuxt. The sources list no fixed version for @nuxt/nitro-server.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA nuxt (nuxt) Fixed in 4.0.0, 4.6.4
  • Fix · CNA nitro-server (@nuxt) Fixed in 4.0.0, 4.6.4
  • Fix · GHSA-hf59-9xwc-2g4p nuxt (npm) Fixed in 4.6.4 Advisory →
  • Fix · GHSA-hf59-9xwc-2g4p @nuxt/nitro-server (npm) Fixed in 4.6.4 Advisory →

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-128076
  2. 2026-11-16 Alias added: GHSA-hf59-9xwc-2g4p
  3. 2026-11-16 Fix available: npm/@nuxt/[email protected], npm/[email protected] · GHSA-hf59-9xwc-2g4p
  4. 2026-11-16 CVSS score added · GHSA-hf59-9xwc-2g4p
  5. 2026-11-16 Weakness changed · GHSA-hf59-9xwc-2g4p
  6. 2026-11-16 5 new references · GHSA-hf59-9xwc-2g4p

References

  • TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
  • TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
  • TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
  • TI-2026-86049 Unauthenticated SQLite function DoS in Nuxt Content query API CVSS 3.1HIGH 7.5
  • TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
  • TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
See all 52 →

Sources