Quick answers
- Is CVE-2026-53722 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53722 being exploited in the wild.
- How severe is CVE-2026-53722?
- Medium severity, with a CVSS score of 4, published 12 June 2026.
- Which products and versions are affected?
- nuxt (npm) SEMVER:introduced=4.0.0,fixed=4.4.7.
- Is there a fix for CVE-2026-53722?
- Yes. nuxt (npm): upgrade to 4.4.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53722 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53722?
- 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.4.7 or later
npm install nuxt@4.4.7
Technical details
A reflected DOM-based Cross-Site Scripting (XSS) vulnerability exists in the <NuxtLink> component due to insufficient validation of URL schemes in the 'to' and 'href' props. The component's external link auto-detection logic failed to reject script-capable protocols like 'javascript:', 'vbscript:', or 'data:'. An attacker can provide a malicious URL that, when rendered and clicked, executes arbitrary JavaScript in the context of the application's origin or facilitates same-tab phishing via 'data:text/html'. The issue is fixed in Nuxt 4.4.7 and 3.21.7 by sanitizing resolved external URLs and stripping script-capable schemes.
Affected products
- Nuxt Nuxt >= 4.0.0, < 4.4.7
- Nuxt Nuxt < 3.21.7
Identifiers
- CVE-2026-53722
- GHSA-934w-87qh-qr26
Timeline
- 2026-06-02: disclosed
- 2026-06-12: advisory: NVD publication
- 2026-06-16: patched: GitHub Advisory reviewed and updated