Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

Nuxt: __nuxt_island endpoint does not bind responses to request props, enabling shared-cache poisoning

CVE-2026-46342GHSA-g8wj-3cr3-6w7v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.4.6, 3.21.6; @nuxt/nitro-server 4.4.6, 3.21.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nuxt

    Affected
    >= 3.1.0, <= 3.21.5>= 4.0.0-alpha.1, <= 4.4.5
    Fixed in
    3.21.6, 4.4.6

  • npm @nuxt/nitro-server

    Affected
    >= 3.20.0, <= 3.21.5>= 4.2.0, <= 4.4.5
    Fixed in
    3.21.6, 4.4.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-46342: 0.09% estimated exploitation activity in the next 30 days; percentile 0.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The /nuxtisland/ 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. Island components are documented as rendering independently of route context - page middleware does not apply to them, and they are intentionally cacheable as a function of their props. This advisory does not treat that contract as a vulnerability. It treats the absence of a binding between the URL the cache keys on and the response served at that URL as one. Impact In applications where a CDN or reverse-proxy in front of the app caches /nuxtisland/ keyed by path only (ignoring query) - a documented misconfiguration class, see GHSA-jvhm-gjrh-3h93 - an attacker can prime the cache for a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g8wj-3cr3-6w7v

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g8wj-3cr3-6w7v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46342

Advisory: Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning
IDs: CVE-2026-46342, GHSA-g8wj-3cr3-6w7v
Record: https://patchnext.com/advisories/cve-2026-46342 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.4.6, 3.21.6; @nuxt/nitro-server 4.4.6, 3.21.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 3.1.0, <= 3.21.5; >= 4.0.0-alpha.1, <= 4.4.5; fixed in 3.21.6, 4.4.6
- npm @nuxt/nitro-server: affected >= 3.20.0, <= 3.21.5; >= 4.2.0, <= 4.4.5; fixed in 3.21.6, 4.4.6

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nuxt/nitro-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt, @nuxt/nitro-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g8wj-3cr3-6w7v (OSV record GHSA-g8wj-3cr3-6w7v lists affected ranges: npm nuxt >=3.1.0 =4.0.0-alpha.1 =3.20.0 =4.2.0 <4.4.6 (fixed))
- Verified: https://github.com/advisories/GHSA-g8wj-3cr3-6w7v (GitHub-reviewed advisory GHSA-g8wj-3cr3-6w7v lists affected ranges: npm nuxt >=3.1.0 =4.0.0-alpha.1 =3.20.0 =4.2.0 <=4.4.5)

Commands are suggestions: review each one before running it.

Loading voting…