# CVE-2026-56698: Nuxt - Cross-Site Scripting via navigateTo open Option

> Attackers can execute arbitrary scripts in the application's origin by supplying javascript: URLs to the navigateTo open option in Nuxt.

- **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:** No
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-h345-75vh-jjwf

## What is CVE-2026-56698?

CVE-2026-56698 is a medium-severity cross-site scripting vulnerability in Nuxt, published on 22 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 versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 fail to validate script-capable URLs in the navigateTo open option, allowing client-side script execution. Attackers can supply javascript: URLs through the open parameter to execute arbitrary scripts in the application's origin when user-controlled input is passed to navigateTo.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Nuxt Nuxt.

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

No fix has been published for CVE-2026-56698 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56698 being exploited?

There is no known exploitation of CVE-2026-56698 in the wild and no public exploit code.

## 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-56698 and fix it if it is affected.

What it is: CVE-2026-56698 is a medium-severity cross-site scripting vulnerability in Nuxt, published on 22 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: There is no known exploitation of CVE-2026-56698 in the wild and no public exploit code.

Affected product: Nuxt. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-56698/ (Markdown: https://insights.sbomify.com/CVE-2026-56698/index.md)
```

## Sources

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

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