CVE-2026-53722

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Nuxt is an open-source web development framework for Vue.js. Prior to versions 3.21.7 and 4.4.7, did not validate the URL scheme of values bound to its to or href props before rendering them into the href attribute of the underlying element. When an application binds attacker-controlled input (a query parameter, a CMS field, a user-supplied profile URL) to or :href, the attacker can supply a javascript: or vbscript: URL that is reflected verbatim into the rendered markup. Clicking the link executes the supplied script in the origin of the Nuxt application, resulting in reflected DOM-based cross-site scripting. A data:text/html,... payload reflected through the same sink does not execute in the application's origin but enables a same-tab phishing surface anchored to a legitimate application link. The same value was exposed to consumers of the component's custom slot via the href and route.href props, so applications that re-bind those values to their own anchors were affected identically. This issue has been patched in versions 3.21.7 and 4.4.7.

CVSS v3
5.4
EG Score
5.4(medium)
EPSS
9.8%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (3)

Auto-updated Jun 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URL · Advisory · nuxt/nuxt · GitHub

https://github.com/nuxt/nuxt/security/advisories/GHSA-934w-87qh-qr26
github_commit

commit 53284043dc21 (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 53284043dc21 — awaiting tagged release

https://github.com/nuxt/nuxt/commit/53284043dc21210a25d629d1cec67d3ae557ffd0
github_commit

commit 0103ce06fbbb (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 0103ce06fbbb — awaiting tagged release

https://github.com/nuxt/nuxt/commit/0103ce06fbbbdfa079a7f020ef8ce00121eac4a3

Vendor Advisories for CVE-2026-53722(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)
PackageVulnerable rangeFixed inDependents
nuxt—3.21.7—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 65× 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.

  1. 2026-07-07 01:15 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 14:12 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 15:06 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 16:14 UTCEG score recompute
  13. 2026-07-02 17:22 UTCEG score recompute
  14. 2026-07-01 18:12 UTCEG score recompute
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 19:19 UTCEG score recompute
  18. 2026-06-29 20:22 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 21:30 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 22:38 UTCEG score recompute
Show 40 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 23:47 UTCEG score recompute
  3. 2026-06-26 00:53 UTCEG score recompute
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 02:01 UTCEG score recompute
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-24 03:09 UTCEG score recompute
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-23 04:14 UTCEG score recompute
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-22 05:17 UTCEG score recompute
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 06:21 UTCEG score recompute
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-20 07:27 UTCEG score recompute
  20. 2026-06-19 19:26 UTCEPSS rescore
  21. 2026-06-19 19:26 UTCEPSS rescore
  22. 2026-06-19 08:28 UTCEG score recompute
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 09:36 UTCEG score recompute
  26. 2026-06-17 17:53 UTCEPSS rescore
  27. 2026-06-17 10:34 UTCEG score recompute
  28. 2026-06-16 17:53 UTCEPSS rescore
  29. 2026-06-16 11:42 UTCEG score recompute
  30. 2026-06-15 17:49 UTCEPSS rescore
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 12:49 UTCEG score recompute▲ 0.30
  33. 2026-06-15 03:24 UTCNVD updateCVSS v3 → 5.4
  34. 2026-06-14 23:18 UTCEPSS rescore
  35. 2026-06-14 13:57 UTCEG score recompute
  36. 2026-06-13 23:00 UTCEPSS rescore
  37. 2026-06-13 15:05 UTCEG score recompute
  38. 2026-06-12 23:12 UTCEPSS rescore
  39. 2026-06-12 16:12 UTCEG score recompute
  40. 2026-06-12 16:12 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53722?
CVE-2026-53722 is a medium vulnerability published on June 12, 2026. Nuxt is an open-source web development framework for Vue.js. Prior to versions 3.21.7 and 4.4.7, <NuxtLink> did not validate the URL scheme of values bound to its to or href props before rendering them into the href attribute of the underlying <a> element. When an application binds…
When was CVE-2026-53722 disclosed?
CVE-2026-53722 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53722 actively exploited?
CVE-2026-53722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53722?
CVE-2026-53722 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-53722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53722, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53722

Explore →

Is Your Infrastructure Affected by CVE-2026-53722?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs