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.
- 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
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.
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 | 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 |
2 more packages
nuxt npm | From 4.0.0-alpha.1 | 4.4.6 |
nuxt npm | From 4.0.0-alpha.1 | 4.4.6 |
Products include 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.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
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 Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
- CVE-2024-23657 Path Traversal: '../filedir' in Nuxt Devtools
- CVE-2024-34344 Remote code execution via the browser when running the test locally in nuxt
- CVE-2024-42352 Server-Side Request Forgery (SSRF) in nuxt-icon
- CVE-2023-3224 Code Injection in nuxt/nuxt
Sources
Also known as GHSA-g8wj-3cr3-6w7v.