Vulnerability in nuxt (CVE-2026-53721)
Summary
Vulnerability in nuxt (CVE-2026-53721). Confidential information can be exposed externally. Exploitable via routeRules. Mitigation: upgrade to 3.21.7 or later.
Original description
The description as published by the source.
Nuxt is an open-source web development framework for Vue.js. From versions 3.11.0 to before 3.21.7 and 4.0.0 to before 4.4.7, there is a route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher. This issue has been patched in versions 3.21.7 and 4.4.7.
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-53721 has been found in nuxt.
Attackers can target a specific entry point like routeRules over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade nuxt to 3.21.7 or later.
If unsure, ask your IT team or search "nuxt CVE-2026-53721" on the vendor's site.
CVE-2026-53721 (nuxt) — CWE-178 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: routeRules / rou3 / appMiddleware / ssr
Patched: 3.21.7 — apply immediately
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.
A vulnerability (CWE-178) exists in nuxt. Attackers reach the vulnerable code path via routeRules without authentication.
Check the vendor advisory for the affected versions of nuxt. Attack surface: routeRules / rou3 / appMiddleware / ssr.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 3.21.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade nuxt to 3.21.7ステージング環境で 3.21.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com