CVE-2026-53722: Reflected DOM-based XSS in Nuxt NuxtLink
- Vendor
- Nuxt
CVE-2026-53722 is a reflected DOM-based cross-site scripting vulnerability in Nuxt's NuxtLink component affecting releases before 3.21.7 on the 3.x branch and before 4.4.7 on the 4.x branch. The component does not validate URL schemes in values bound to its to or href properties before rendering them into an anchor's href attribute. Attacker-controlled javascript: or vbscript: URLs can therefore execute script in the application's origin when clicked. Unsafe values are also exposed through the custom slot's href and route.href properties, affecting applications that bind those values to their own anchors. A data:text/html URL enables same-tab phishing rather than script execution in the application's origin.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality and integrity of a victim's application session through attacker-controlled script execution. Potential consequences include theft of script-accessible session information and CSRF tokens, DOM modification, credential harvesting, and account takeover where the victim's privileges and application controls permit it. HTML data URLs can instead display attacker-controlled phishing content in the same tab after the victim follows an apparently legitimate application link.
Mitigation
If you can’t patch tonight, do this now.
Validate attacker-influenced destinations before binding them to NuxtLink or custom anchors. Prefer allowing only application-relative paths beginning with a single slash, rejecting protocol-relative URLs and other URL forms. If external destinations are necessary, parse and normalize them with a URL parser and allow only explicitly approved protocols such as HTTP and HTTPS. Apply the same validation to custom-slot href values. A strict Content Security Policy can provide defense in depth but should not replace destination validation or upgrading.
Remediation
Patch, then assume compromise.
The initial fix is available in Nuxt 3.21.7 and 4.4.7. It introduces sanitizeExternalHref to reject script-capable protocols, suppress unsafe href values, and refuse navigation. A subsequent vulnerability, CVE-2026-114130, bypasses that fix in applications with pages disabled and affects all Nuxt 3 releases and Nuxt 4 releases before 4.6.0. Upgrade to Nuxt 4.6.0 or later to address both issues. Nuxt 3 reached end of life on July 31, 2026; affected Nuxt 3 deployments should migrate to a fixed Nuxt 4 release.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-53722 exploited in the wild?
- As of Oct 23, 2026, Mallory has no reports of CVE-2026-53722 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-53722?
- As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-53722.
- Is there a patch for CVE-2026-53722?
- The initial fix is available in Nuxt 3.21.7 and 4.4.7. It introduces sanitizeExternalHref to reject script-capable protocols, suppress unsafe href values, and refuse navigation.
- What products are affected by CVE-2026-53722?
- Nuxt.
- How severe is CVE-2026-53722?
- CVE-2026-53722 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.29% (22nd percentile) as of Oct 23, 2026.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.