← Back
CVE-2026-53721
high
CVSS 8.2
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-178) exists in nuxt. Attackers reach the vulnerable code path via ``routeRules`` without authentication.
📍 Affected scope
nuxt — . Attack surface: `routeRules` / `rou3` / `appMiddleware` / `ssr`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.21.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
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/07e39cd6f26e407b4192b7865bd17bc44536b9bb
- web https://github.com/nuxt/nuxt/commit/3f3e3fa7b5eec8e495f4f8ce0a54813a8875a11e
- web https://github.com/nuxt/nuxt/security/advisories/GHSA-mm7m-92g8-7m47
- web https://nvd.nist.gov/vuln/detail/CVE-2026-53721
- web https://github.com/advisories/GHSA-mm7m-92g8-7m47