Nuxt: Unauthorized Component Instantiation via Server Island Props

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-71318: 0.32% estimated exploitation activity in the next 30 days; percentile 24.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Nuxt server islands accept props via the /nuxtisland/ endpoint. When an application has a server island component that forwards props directly into Vue's dynamic component resolution (<component :is, resolveDynamicComponent, or h()), an attacker can pass a plain string value (rather than a component definition) to instantiate any globally-registered Vue component or any native HTML element. For example: ...resolves and renders SomeGlobalComponent if it is globally registered, even though the attacker should only be able to drive props for the island's declared component. Similarly, { "as": "iframe" } renders an <iframe element. Unlike the primary RCE vector (GHSA-9473-5f9j-94wq), this does not require vue.runtimeCompiler to be enabled. A plain string prop is sufficient to trigger component resolution. The template/render key guard that addresses the RCE vector does not block plain string values. Some component libraries expose a polymorphic as / asChild prop that forwards its…

Published by the source

5 Aug 2026, 21:21 UTC

Last modified by the source

5 Aug 2026, 21:21 UTC

Source last checked

26 Oct 2026, 13:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-48hr-524c-v5w3

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

# Patch Next advisory brief: CVE-2026-71318

Advisory: Nuxt: Unauthorized Component Instantiation via Server Island Props
IDs: CVE-2026-71318, GHSA-48hr-524c-v5w3
Record: https://patchnext.com/advisories/cve-2026-71318 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.5.1, 3.21.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.0.0, < 4.5.1; >= 3.1.0, < 3.21.10; fixed in 3.21.10, 4.5.1

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

## 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.
- 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://github.com/advisories/GHSA-48hr-524c-v5w3 (GitHub-reviewed advisory GHSA-48hr-524c-v5w3 lists affected ranges: npm nuxt >=4.0.0 =3.1.0 <3.21.10)

Commands are suggestions: review each one before running it.