CVE-2026-53722: Nuxt · Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URL
Affects nuxtSource GCVE Database
Not known to be exploited · CVSS 5.1 Medium : upgrade to 4.4.7 when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.4.7, 3.21.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade nuxt to 4.4.7; nuxt to 3.21.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnuxt | Affected
| Fixed in
|
| npmnuxt | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in nuxt@4.4.7 and nuxt@3.21.7. Upgrade to these or later versions to remediate the vulnerability. The fix sanitizes external href values by stripping control characters and whitespace, unwrapping 'view-source:' prefixes, and replacing script-capable URL schemes with an empty string before rendering. Until upgrading, validate URLs at the source before binding them to <NuxtLink :to> or :href, for example by only accepting paths starting with '/' or by using URL parsing to allow only safe protocols such as 'http:' and 'https:'.
Description
Nuxt versions prior to 4.4.7 and 3.21.7 contain a reflected DOM-based cross-site scripting (XSS) vulnerability in the <NuxtLink> component. This occurs because the component does not validate URL schemes in its 'to' or 'href' props, allowing attacker-controlled inputs with 'javascript:', 'vbscript:', or 'data:' URLs to be rendered directly into anchor href attributes. Clicking such links can execute malicious scripts in the application's origin or enable phishing attacks. The issue affects applications that bind user input to <NuxtLink> URLs, such as user profiles, CMS fields, or marketplace listings. The vulnerability is fixed in nuxt@4.4.7 and nuxt@3.21.7 by sanitizing and rejecting script-capable URL schemes before rendering.
References
- github.com/nuxt/nuxt/security/advisories/GHSA-934w-87qh-qr26 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-53722 (opens in a new tab)
- github.com/nuxt/nuxt/commit/0103ce06fbbbdfa079a7f020ef8ce00121eac4a3 (opens in a new tab)
- github.com/nuxt/nuxt/commit/53284043dc21210a25d629d1cec67d3ae557ffd0 (opens in a new tab)
- github.com/nuxt/nuxt (opens in a new tab)