What is CVE-2026-71320?
Nuxt is an open-source web development framework for Vue.js. From 3.4.0 until 3.21.10 and 4.5.1, an attacker can inject a template key through /__nuxt_island/ props into a dynamic component when `vue.runtimeCompiler: true` is enabled, causing template execution in the Nitro process. This issue is fixed in 3.21.10 and 4.5.1.
The record classifies CVE-2026-71320 under weakness classes CWE-74, CWE-94. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 61 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.1 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.4% probability of exploitation in the next 30 days, higher than 36.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 5.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-05, last modified 2026-08-06
Is CVE-2026-71320 being exploited?
It currently carries a trending score of 39 in the Threadlinqs vulnerability feed.
Affected products and versions
- nuxt: nuxt
Affected software packages:
npm:nuxt— patched in 4.5.1npm:nuxt— patched in 3.21.10
How to fix CVE-2026-71320
Fixed versions are recorded for 2 packages: npm:nuxt 4.5.1, npm:nuxt 3.21.10. No vendor patch reference has been recorded for CVE-2026-71320 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-71320
No threat campaign in the Threadlinqs corpus currently references CVE-2026-71320, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .