All vulnerabilities

Servers and applications

CVE-2026-71318

Unauthorized Component Instantiation via Server Island Props in Nuxt

Severity
Medium 4.8
Published
27 Jul 2026
Last changed
5 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.21.10, 4.5.1
Exploit chance
0.3% in the next 30 daysHigher than 24% of CVEs. EPSS by FIRST, 18 Nov 2026
Weakness
Improper input validation (CWE-20)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read some data · Change some data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Also known as
GHSA-48hr-524c-v5w3
Sources
Project advisories (GitHub)

Description

Nuxt server islands accept props via the /__nuxt_island/ endpoint. When an application has a server island component that forwards props directly into Vue's dynamic component resolution (, 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 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.

From nuxt/nuxt's security advisory. Shortened; the full text is there.

Workarounds

Upgrade to [email protected] or [email protected]. That upgrade also removes the related object-prop RCE (GHSA-9473-5f9j-94wq). In addition, in any version:

  • Do not forward island props into , resolveDynamicComponent, or h()`. Map an untrusted discriminator through a closed allowlist of imported component definitions instead of passing the raw prop value.
  • Declare the props an island accepts, or set inheritAttrs: false on it, so request input cannot fall through to a polymorphic root component.
  • Avoid registering sensitive components globally that could leak information if instantiated by an attacker.
Workarounds as given by nuxt/nuxt's security advisory.

Affected software

SoftwareAffected versions
NuxtServers and applications · github:nuxt/nuxt
  • From 3.1.0 before 3.21.10
  • From 4.0.0 before 4.5.1

About Nuxt

JavaScript framework

From Wikidata, CC0 1.0.
Developers who used it in the past year
4%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
3,404,733npm, 15 Nov 2026
GitHub stars
61,078GitHub, 15 Nov 2026
Forks
5,837GitHub, 15 Nov 2026
Latest release
v4.6.4GitHub, 15 Nov 2026
Released
2 Nov 2026GitHub
License
MIT LicenseWikidata
Written in
JavaScript, Vue.jsWikidata
First published on GitHub
26 Oct 2016GitHub

Release lines

ReleaseLatestSecurity fixes
44.6.4Yes
33.21.11Ended 31 Jul 2026
22.18.1Ended 30 Jun 2024
11.4.5Ended 21 Sept 2019

From endoflife.date.

References