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

> Attackers can execute arbitrary code by injecting malicious props into Nuxt server island endpoints, requiring an upgrade to patched versions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-48hr-524c-v5w3

## What is CVE-2026-71318?

CVE-2026-71318 is a medium-severity code injection vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-71318?

4 open source packages ship an affected version, including nuxt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.1.0 | 3.21.10 |
| `nuxt` | npm | From 3.1.0 | 3.21.10 |
| `nuxt` | npm | From 4.0.0 | 4.5.1 |
| `nuxt` | npm | From 4.0.0 | 4.5.1 |

## How do I fix CVE-2026-71318?

Upgrade nuxt to a fixed version for your release line: 3.21.10 or 4.5.1.

## Is CVE-2026-71318 being exploited?

There is no known exploitation of CVE-2026-71318 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71318 and fix it if it is affected.

What it is: CVE-2026-71318 is a medium-severity code injection vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71318 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected from 3.1.0; fixed in 3.21.10
- nuxt (npm): affected from 3.1.0; fixed in 3.21.10
- nuxt (npm): affected from 4.0.0; fixed in 4.5.1
- nuxt (npm): affected from 4.0.0; fixed in 4.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71318/ (Markdown: https://insights.sbomify.com/CVE-2026-71318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71318
- OSV: https://osv.dev/vulnerability/CVE-2026-71318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71318/
Summaries are generated and may contain mistakes; the official description above is the record.