← Back
CVE-2026-56326
medium
CVSS 6.1
Open Redirect in nuxt (CVE-2026-56326)
Summary
vulnerability in nuxt (CVE-2026-56326). Risk of unauthorized operations or information disclosure. Exploitable via ``navigateTo``. Mitigation: upgrade to `3.21.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-56326** has been found in nuxt.
Attackers can target a specific entry point like ``navigateTo`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade nuxt to **3.21.7** or later.
If unsure, ask your IT team or search "nuxt CVE-2026-56326" on the vendor's site.
CVE-2026-56326 (nuxt) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `navigateTo` / `reloadNuxtApp` / `Location` / `isScriptProtocol`
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-601) exists in nuxt. Attackers reach the vulnerable code path via ``navigateTo`` without authentication.
📍 Affected scope
nuxt — . Attack surface: `navigateTo` / `reloadNuxtApp` / `Location` / `isScriptProtocol`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure
🔧 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
- advisory [email protected]
- advisory [email protected]
- patch [email protected]
- patch [email protected]
- web https://github.com/nuxt/nuxt/pull/35115
- web https://github.com/nuxt/nuxt/pull/35206
- web https://github.com/nuxt/nuxt/commit/3394716d4a913cba904b028df5338f2aead50032
- web https://github.com/nuxt/nuxt/commit/62fc32eddf648b00a3890141e0235d2a222b024d
- web https://github.com/nuxt/nuxt/commit/6497d99dd106254abd089f6a263d7773869a343b
- web https://github.com/nuxt/nuxt/commit/e447a793c47766834f7497f8412a76cd56fd8ee1
- web https://github.com/advisories/GHSA-c9cv-mq2m-ppp3