Quick answers
- Is CVE-2026-71314 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71314 being exploited in the wild.
- How severe is CVE-2026-71314?
- High severity, with a CVSS score of 7.5, published 5 August 2026.
- Which products and versions are affected?
- nuxt (npm) SEMVER:introduced=4.0.0,fixed=4.5.1.
- Is there a fix for CVE-2026-71314?
- Yes. nuxt (npm): upgrade to 4.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71314 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-71314?
- Check whether you run nuxt (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nuxt (npm): upgrade to 4.5.1 or later
npm install nuxt@4.5.1
Technical details
Nuxt is vulnerable to uncontrolled resource consumption (CWE-400) within its island rendering engine. The vulnerability exists because the island URL hash is a non-secret digest, allowing an attacker to compute valid hashes for arbitrary props. By sending a large integer as a prop to a component using 'v-for' (e.g., v-for='n in count'), the server attempts to expand the loop into millions of nodes during Server-Side Rendering (SSR). This results in excessive memory allocation and an out-of-memory (OOM) crash of the worker process. The issue affects both Vue's 'ssrRenderList' and the 'vforToArray' slot helper. Patches in versions 4.5.1 and 3.21.10 introduce a 'MAX_VFOR_LENGTH' clamp of 100,000 iterations to mitigate this amplification.
Affected products
- Nuxt Nuxt >= 4.0.0, < 4.5.1; >= 3.1.0, < 3.21.10
Identifiers
- CVE-2026-71314
- GHSA-hxcr-hm88-mpq6
Timeline
- 2026-07-27: disclosed
- 2026-08-05: advisory
- 2026-08-05: patched