Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71320 – Server-Side Remote Code Execution – Nuxt 3.4.0–3.21.9 and 4.0.0–4.5.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71320 is a server-side remote code execution vulnerability in the Server Island feature of Nuxt. Attacker-controlled island props are forwarded to Vue’s runtime compiler, allowing injected template code to execute within the Nitro server process. It affects Nuxt 3.4.0–3.21.9 and 4.0.0–4.5.0 and is rated High (CVSS 8.1).

Technical details

  • Root cause: Island component props are insufficiently validated before being forwarded to Vue’s dynamic component resolution, letting an attacker inject a template (or render) key containing executable code that Vue’s runtime compiler then executes on the server.
  • Trigger conditions (all required): vue.runtimeCompiler: true is configured (off by default); the application exposes a .server.vue component that forwards attacker-controlled props into <component :is>, resolveDynamicComponent(), h(), or polymorphic as/asChild props; and the attacker submits crafted props to the /__nuxt_island/ endpoint.
  • Attack vector: Network, no authentication or user interaction required; high attack complexity due to the required non-default configuration.
  • Impact: Execution of attacker-supplied template code within the Nitro process, compromising confidentiality, integrity, and availability.

Affected software

  • Nuxt 3.4.0 through 3.21.9
  • Nuxt 4.0.0 through 4.5.0
  • Earlier versions are unaffected due to compiler dependency mocking on the server.

Severity

  • CVSS v3.1 base score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Nuxt 3.21.10 or 4.5.1.
  • If no patch can be applied:
    • Ensure vue.runtimeCompiler remains false (its default value).
    • Avoid forwarding island props into dynamic component paths without sanitization.
    • Deploy WAF rules blocking requests containing template or render keys in decoded /__nuxt_island/ props. Note that WAF filtering does not cover initial server-side rendering paths.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <div id="__nuxt", window.__NUXT__
  • URL of a loaded script: /_nuxt/
  • JavaScript object present once the page runs: $nuxt

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge