Cross-Site Scripting (XSS) in nuxt (CVE-2026-53722)
Summary
Cross-site scripting in nuxt (CVE-2026-53722). Risk of unauthorized operations or information disclosure. Exploitable via href. Mitigation: upgrade to 3.21.7 or later.
Original description
The description as published by the source.
Summary
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.
Unlike the previously reported navigateTo issue (CVE-2024-34343), the sink here is the rendered anchor itself; the existing isScriptProtocol checks in navigateTo and reloadNuxtApp are not on the code path. The onClick handler intentionally returns early for external links so the browser's native protocol-based navigation runs.
Affected component
- File:
packages/nuxt/src/app/components/nuxt-link.ts - Sink:
h('a', { href: href.value, ... })in the default render, plus thehref/route.hrefprops passed to thecustomslo…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53722 has been found in nuxt.
Attackers can target a specific entry point like href over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade nuxt to 3.21.7 or later.
If unsure, ask your IT team or search "nuxt CVE-2026-53722" on the vendor's site.
CVE-2026-53722 (nuxt) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: href / custom / route.href / navigateTo
Patched: 3.21.7 — apply immediately
Workaround: Until you can upgrade, validate URLs at the source before binding them to <NuxtLink :to> / :href.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in nuxt. Attackers reach the vulnerable code path via href without authentication.
Check the vendor advisory for the affected versions of nuxt. Attack surface: href / custom / route.href / navigateTo.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.21.7.
Workaround: Until you can upgrade, validate URLs at the source before binding them to <NuxtLink :to> / :href.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nuxt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nuxt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nuxtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Until you can upgrade, validate URLs at the source before binding them to `<NuxtLink :to>` / `:href`.パッチが適用されるまでの応急処置として、Until you can upgrade, validate URLs at the source before binding them to
<NuxtLink :to>/:href. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade nuxt to 3.21.7ステージング環境で 3.21.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com