← Back
CVE-2026-53722
medium
CVSS 5.4
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in nuxt. Attackers reach the vulnerable code path via ``href`` without authentication.
📍 Affected scope
nuxt — . Attack surface: `href` / `custom` / `route.href` / `navigateTo`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.21.7**.
🛡️ Workaround
Workaround: Until you can upgrade, validate URLs at the source before binding them to `<NuxtLink :to>` / `:href`.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply 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`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade nuxt to 3.21.7ステージング環境で 3.21.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
nuxt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.21.7"}]}]
References
- web https://github.com/nuxt/nuxt/commit/0103ce06fbbbdfa079a7f020ef8ce00121eac4a3
- web https://github.com/nuxt/nuxt/commit/53284043dc21210a25d629d1cec67d3ae557ffd0
- web https://github.com/nuxt/nuxt/security/advisories/GHSA-934w-87qh-qr26
- web https://nvd.nist.gov/vuln/detail/CVE-2026-53722
- web https://github.com/advisories/GHSA-934w-87qh-qr26