# CVE-2026-45669: Nuxt: Reflected XSS in `navigateTo()` external redirect

> Attackers can inject arbitrary JavaScript via external redirects in Nuxt, leading to code execution under the application's origin.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-fx6j-w5w5-h468

## What is CVE-2026-45669?

CVE-2026-45669 is a medium-severity cross-site scripting vulnerability in nuxt, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Nuxt is an open-source web development framework for Vue.js. From versions 3.4.3 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6, navigateTo() with external: true generates a server-side HTML redirect body containing a <meta http-equiv="refresh"> 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 issue has been patched in versions 3.21.6 and 4.4.6.

Weakness: CWE-83 (Improper Neutralization of Script in Attributes in a Web Page)

## Which versions are affected by CVE-2026-45669?

4 open source packages ship an affected version, including nuxt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.4.3 | 3.21.6 |
| `nuxt` | npm | From 3.4.3 | 3.21.6 |
| `nuxt` | npm | From 4.0.0-alpha.1 | 4.4.6 |
| `nuxt` | npm | From 4.0.0-alpha.1 | 4.4.6 |

Products: Nuxt Nuxt.

## How do I fix CVE-2026-45669?

Upgrade nuxt to a fixed version for your release line: 3.21.6 or 4.4.6.

## Is CVE-2026-45669 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45669 exists.

## Other vulnerabilities in nuxt

- [CVE-2026-53721](https://insights.sbomify.com/CVE-2026-53721/): Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher (high 8.8)
- [CVE-2024-23657](https://insights.sbomify.com/CVE-2024-23657/): Path Traversal: '../filedir' in Nuxt Devtools (high 8.8)
- [CVE-2024-34344](https://insights.sbomify.com/CVE-2024-34344/): Remote code execution via the browser when running the test locally in nuxt (high 8.8)
- [CVE-2024-42352](https://insights.sbomify.com/CVE-2024-42352/): Server-Side Request Forgery (SSRF) in nuxt-icon (high 8.6)
- [CVE-2023-3224](https://insights.sbomify.com/CVE-2023-3224/): Code Injection in nuxt/nuxt (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45669 and fix it if it is affected.

What it is: CVE-2026-45669 is a medium-severity cross-site scripting vulnerability in nuxt, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45669 exists.

Affected packages and fixed versions:
- nuxt (npm): affected from 3.4.3; fixed in 3.21.6
- nuxt (npm): affected from 3.4.3; fixed in 3.21.6
- nuxt (npm): affected from 4.0.0-alpha.1; fixed in 4.4.6
- nuxt (npm): affected from 4.0.0-alpha.1; fixed in 4.4.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45669/ (Markdown: https://insights.sbomify.com/CVE-2026-45669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45669
- OSV: https://osv.dev/vulnerability/CVE-2026-45669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45669/
Summaries are generated and may contain mistakes; the official description above is the record.