Loading vulnerability…
CVE-2026-71314 is an unauthenticated denial-of-service vulnerability in Nuxt affecting server-side rendering of server islands. In vulnerable versions, the server island rendering mechanism accepts attacker-controlled props that can reach template expressions such as v-for loops without adequate server-side bounds checking. Because the request-signing mechanism for island rendering is deterministic and does not rely on a server-side secret, an external attacker can forge valid island-rendering requests and supply malicious numeric input to loop expressions such as v-for="n in count". During SSR, this can trigger unbounded iteration and large memory allocations as the runtime attempts to create virtual nodes and output structures for an attacker-supplied loop count. The resulting excessive heap consumption can terminate the Node.js process with an out-of-memory condition. Fixed releases introduce server-side bounds enforcement for v-for sources used in this rendering path.
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.
Patch, then assume compromise.
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.
4 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.