Loading vulnerability…
CVE-2026-71320 is a server-side code execution vulnerability in Nuxt affecting versions 3.4.0 through before 3.21.10 and 4.0.0 through before 4.5.1. When vue.runtimeCompiler: true is enabled, an attacker can inject a template key through props supplied to the __nuxt_island endpoint and have that data reach a dynamic component. This can cause attacker-controlled template compilation and execution inside the Nitro process. The flaw arises from unsafe handling of attacker-influenced component props in conjunction with Vue runtime template compilation and dynamic component resolution. The issue is associated with improper neutralization of special elements in input used by a downstream component and code generation from externally controlled input.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
vue.runtimeCompiler by setting it to false, which is the default. Avoid passing untrusted island props into dynamic component resolution paths such as <component :is>, resolveDynamicComponent, or h() without strict sanitization and validation. As a compensating control, deploy filtering on requests targeting the Nuxt island rendering path that decodes and parses submitted props and blocks objects containing dangerous keys such as template or render. This should be treated only as a temporary mitigation because edge filtering may not cover all internal SSR island render paths.Patch, then assume compromise.
template key at any depth when vue.runtimeCompiler is enabled. Ensure all affected deployments are updated to a patched release in the applicable major version line.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.