# CVE-2026-46342: Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning

> Attackers can poison shared caches by manipulating props in Nuxt island endpoints, leading to cross-site scripting and data modification.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-g8wj-3cr3-6w7v

## What is CVE-2026-46342?

CVE-2026-46342 is a low-severity cross-site scripting vulnerability in nuxt, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Nuxt is an open-source web development framework for Vue.js. In Nuxt versions 3.1.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6 and @nuxt/nitro-server versions 3.20.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6, the /__nuxt_island/* endpoint accepts attacker-controlled props query/body parameters and renders any island component without verifying that the URL-resident hash (<Name>_<hashId>.json) was actually issued for those inputs by <NuxtIsland>. The hash is computed and embedded client-side but never validated server-side, so the same path can return materially different responses depending on the query. This issue has been patched in versions 3.21.6 and 4.4.6.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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

8 open source packages ship an affected version, including @nuxt/nitro-server and nuxt. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nuxt/nitro-server` | npm | From 3.20.0 | 3.21.6 |
| `@nuxt/nitro-server` | npm | From 3.20.0 | 3.21.6 |
| `@nuxt/nitro-server` | npm | From 4.2.0 | 4.4.6 |
| `@nuxt/nitro-server` | npm | From 4.2.0 | 4.4.6 |
| `nuxt` | npm | From 3.1.0 | 3.21.6 |
| `nuxt` | npm | From 3.1.0 | 3.21.6 |
| `nuxt` | npm | From 4.0.0-alpha.1 | 4.4.6 |
| `nuxt` | npm | From 4.0.0-alpha.1 | 4.4.6 |

Products: Nuxt Nuxt, Nuxt Nuxt\/Nitro-Server.

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

Upgrade @nuxt/nitro-server to a fixed version for your release line: 3.21.6 or 4.4.6.

## Is CVE-2026-46342 being exploited?

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

## Other vulnerabilities in nuxt

- [CVE-2026-53721](https://insights.sbomify.com/CVE-2026-53721/): Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher (high 8.8)
- [CVE-2024-23657](https://insights.sbomify.com/CVE-2024-23657/): Path Traversal: '../filedir' in Nuxt Devtools (high 8.8)
- [CVE-2024-34344](https://insights.sbomify.com/CVE-2024-34344/): Remote code execution via the browser when running the test locally in nuxt (high 8.8)
- [CVE-2024-42352](https://insights.sbomify.com/CVE-2024-42352/): Server-Side Request Forgery (SSRF) in nuxt-icon (high 8.6)
- [CVE-2023-3224](https://insights.sbomify.com/CVE-2023-3224/): Code Injection in nuxt/nuxt (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46342 is a low-severity cross-site scripting vulnerability in nuxt, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-46342 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/nitro-server (npm): affected from 3.20.0; fixed in 3.21.6
- @nuxt/nitro-server (npm): affected from 3.20.0; fixed in 3.21.6
- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.4.6
- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.4.6
- nuxt (npm): affected from 3.1.0; fixed in 3.21.6
- nuxt (npm): affected from 3.1.0; fixed in 3.21.6
- nuxt (npm): affected from 4.0.0-alpha.1; fixed in 4.4.6
- nuxt (npm): affected from 4.0.0-alpha.1; fixed in 4.4.6

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-46342/ (Markdown: https://insights.sbomify.com/CVE-2026-46342/index.md)
```

## Sources

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

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