# CVE-2026-56317: Nuxt - Cross-Site Scripting via NoScript Component Slot Content

> Attackers can execute arbitrary scripts in the victim's browser via untrusted data in Nuxt NoScript component slots.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/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:** 20 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** CLSA-2026-1788337370, CLSA-2026-1788522007, CLSA-2026-1788960197, CLSA-2026-1792161461, CLSA-2026-1792161602, CLSA-2026-1792161824, CLSA-2026-1792161937, GHSA-m3q2-p4fw-w38m

## What is CVE-2026-56317?

CVE-2026-56317 is a low-severity cross-site scripting vulnerability in Nuxt, published on 20 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 before 4.4.7 (and the 3.x branch before 3.21.7) contains a cross-site scripting vulnerability in the NoScript component that writes slot content to innerHTML without escaping. Attackers can inject malicious scripts through untrusted data in NoScript slots, such as route.query parameters, which execute in the document context when the noscript tag is implicitly closed by script tags.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | All versions | 3.21.7 |
| `nuxt` | npm | All versions | 3.21.7 |
| `nuxt` | npm | From 4.0.0 | 4.4.7 |
| `nuxt` | npm | From 4.0.0 | 4.4.7 |

Products: Nuxt Nuxt.

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

Upgrade nuxt to a fixed version for your release line: 3.21.7 or 4.4.7.

## Is CVE-2026-56317 being exploited?

There is no known exploitation of CVE-2026-56317 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-56317 and fix it if it is affected.

What it is: CVE-2026-56317 is a low-severity cross-site scripting vulnerability in Nuxt, published on 20 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-56317 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected all versions; fixed in 3.21.7
- nuxt (npm): affected all versions; fixed in 3.21.7
- nuxt (npm): affected from 4.0.0; fixed in 4.4.7
- nuxt (npm): affected from 4.0.0; fixed in 4.4.7

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

## Sources

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

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