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


- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DHI-gxqq-j5if-vbwy-jrw6, GHSA-hf59-9xwc-2g4p

## What is CVE-2026-128076?

CVE-2026-128076 is a low-severity vulnerability in @nuxt nitro-server, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-128076?

4 open source packages ship an affected version, including @nuxt/nitro-server and nuxt.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `@nuxt/nitro-server` | npm | `pkg:npm/%40nuxt/nitro-server` | From 3.21.6 | None |
| `@nuxt/nitro-server` | npm | `pkg:npm/%40nuxt/nitro-server` | From 4.4.6 | 4.6.4 |
| `nuxt` | npm | `pkg:npm/nuxt` | From 3.21.6 | None |
| `nuxt` | npm | `pkg:npm/nuxt` | From 4.4.6 | 4.6.4 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@nuxt/nitro-server`, `nuxt` | 4.6.4 |

## How do I fix CVE-2026-128076?

Upgrade @nuxt/nitro-server to 4.6.4 or later.

## Is CVE-2026-128076 being exploited?

There is no known exploitation of CVE-2026-128076 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128076 and fix it if it is affected.

What it is: CVE-2026-128076 is a low-severity vulnerability in @nuxt nitro-server, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128076 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/nitro-server (npm): affected from 3.21.6; no fix listed
- @nuxt/nitro-server (npm): affected from 4.4.6; fixed in 4.6.4
- nuxt (npm): affected from 3.21.6; no fix listed
- nuxt (npm): affected from 4.4.6; fixed in 4.6.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128076/ (Markdown: https://insights.sbomify.com/CVE-2026-128076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128076
- OSV: https://osv.dev/vulnerability/CVE-2026-128076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128076/
Summaries are generated and may contain mistakes; the official description above is the record.
