Nuxt is an open-source web development framework for Vue.js. From 3.1.0 until 3.21.10 and 4.5.1, an unauthenticated attacker can use a server island v-for prop, including vforToArray and , to trigger unbounded SSR memory allocation until MAX_VFOR_LENGTH = 100000 and crash the Nuxt process. This issue is fixed in 3.21.10 and 4.5.1.
CVE-2026-71314
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 6, 2026
Advisory Details (5)
Auto-updated Aug 5, 2026Unauthenticated out-of-memory crash via unbounded v-for expansion in Nuxt island rendering · Advisory · nuxt/nuxt · GitHub
https://github.com/nuxt/nuxt/security/advisories/GHSA-hxcr-hm88-mpq6Release v4.5.1 (nuxt/nuxt)
Patch available: nuxt/nuxt v4.5.1
https://github.com/nuxt/nuxt/releases/tag/v4.5.1Release v3.21.10 (nuxt/nuxt)
Patch available: nuxt/nuxt v3.21.10
https://github.com/nuxt/nuxt/releases/tag/v3.21.10commit 668cdfdfda41 (nuxt/nuxt)
Fix landed in nuxt/nuxt commit 668cdfdfda41 — awaiting tagged release
https://github.com/nuxt/nuxt/commit/668cdfdfda41849ed11c1ee5e2067a11fc103b22commit 4e35ae9babd9 (nuxt/nuxt)
Fix landed in nuxt/nuxt commit 4e35ae9babd9 — awaiting tagged release
https://github.com/nuxt/nuxt/commit/4e35ae9babd94be53246e31200232d48438bb34eVendor Advisories for CVE-2026-71314(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nuxt | — | 3.21.10 | — |
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 19:55 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 20:34 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:05 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 09:21 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 09:53 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-13 22:40 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:11 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 23:42 UTCEG score recompute
- 2026-08-11 00:12 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:37 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 01:09 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
Show 6 moreShow fewer
- 2026-08-08 01:40 UTCEG score recompute
- 2026-08-06 14:28 UTCEG score recompute
- 2026-08-06 13:53 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 21:17 UTCEG score recompute
- 2026-08-05 21:07 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-1284 · CWE-400 · CWE-770
- CVE-2010-3904NVD 7.8EG 9.0 KEVEPSS p96CRITICAL
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS p91CRITICAL
- CVE-2010-3705EG 8.3HIGH
- CVE-2006-1364NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS p99HIGH
- CVE-2012-0024EG 7.8HIGH
- CVE-2011-3192EG 7.8EPSS p100HIGH
- CVE-2010-4686EG 7.8HIGH
- CVE-2010-4671EG 7.8HIGH
- CVE-2009-2054EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-71314?
When was CVE-2026-71314 disclosed?
Is CVE-2026-71314 actively exploited?
What is the CVSS score of CVE-2026-71314?
How do I remediate CVE-2026-71314?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71314
Is Your Infrastructure Affected by CVE-2026-71314?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.