Vulnerability in nuxt (CVE-2026-45669)
Summary
Vulnerability in nuxt (CVE-2026-45669). Risk of unauthorized operations or information disclosure. Exploitable via Location. Mitigation: upgrade to 4.4.6 or later.
Original description
The description as published by the source.
Summary
navigateTo() with external: true generates a server-side HTML redirect body containing a `` tag. The destination URL is only sanitized by replacing " with %22, leaving <, >, &, and ' unencoded. An attacker who can influence the URL passed to navigateTo(url, { external: true }) can break out of the content="…" attribute and inject arbitrary HTML/JavaScript that executes under the application's origin.
This is a different root cause from CVE-2024-34343 (GHSA-vf6r-87q4-2vjf), which addressed javascript: protocol bypass. The issue here is triggered by any valid URL containing >.
Impact
Applications that pass user-controlled input to navigateTo(url, { external: true }) — typically via a ?next= / ?redirect= query parameter used for post-login or "return to" flows — are vulnerable to reflected cross-site scripting. The injected script runs in the context of the application's origin during the server-rendered redirect response, before the meta-refresh fires.
Details
In packages/nuxt/src/app/composables/router.ts, the SSR redirect path builds an HTML response body with only " percent-encoded in the destination URL:
const encodedLoc = location.replace(/"/g, '%22')
nuxtApp.ssrContext!['~renderResponse'] = {
status: sanitizeStatusCode(options?.redirectCode || 302, 302),
body: `<!DOCTYPE html>`,
headers: { location: encodeURL(location, isExternalHost) },
}
The Location header is normalised through encodeURL() (which…
Source: GitHub Security Advisories (Global) 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-45669 has been found in nuxt.
Attackers can target a specific entry point like Location 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 4.4.6 or later.
If unsure, ask your IT team or search "nuxt CVE-2026-45669" on the vendor's site.
CVE-2026-45669 (nuxt) — CWE-83 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Location / URL / navigateTo
Patched: 4.4.6 — apply immediately
Workaround: If you can't upgrade immediately, validate user-controlled URLs before passing them to navigateTo(url, { external: true }).
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-83) exists in nuxt. Attackers reach the vulnerable code path via Location without authentication.
Check the vendor advisory for the affected versions of nuxt. Attack surface: Location / URL / navigateTo.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 4.4.6.
Workaround: If you can't upgrade immediately, validate user-controlled URLs before passing them to navigateTo(url, { external: true }).
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
If you can't upgrade immediately, validate user-controlled URLs before passing them to `navigateTo(url, { external: true })`.パッチが適用されるまでの応急処置として、If you can't upgrade immediately, validate user-controlled URLs before passing them to
navigateTo(url, { external: true }). を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade nuxt to 4.4.6ステージング環境で 4.4.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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