CVE-2026-56317: Nuxt before 4.4.7 (and the 3.x branch before 3.21.7) contains a cross-site scripting vulnerability in the NoSc

Routine

MEDIUM 6.1UPGRADE

CVE-2026-56317 is a medium-severity flaw (CVSS 6.1) affecting nuxt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-06-20
Last modified	2026-06-24

Publisher (CNA): VulnCheck · Vendor: nuxt

Last updated 2026-06-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-20 16:17 UTCPublished CVE record published
2026-06-24 19:17 UTCUpdated Record last modified

nuxt nuxt UPGRADE

Affected: < 3.21.7 · >= 4.0.0 and < 4.4.7

Fixed in: 3.21.7, 4.4.7

Safe to downgrade to: a release before 4.0.0

1. Check installed version

apt-cache policy nuxt || rpm -q nuxt || nuxt --version

2. UPGRADE to 3.21.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nuxt

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nuxt

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)

apt-cache madison nuxt sudo apt install nuxt=<VERSION_BEFORE_4.0.0> sudo apt-mark hold nuxt

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list nuxt sudo dnf downgrade nuxt-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add nuxt

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-56317?

nuxt: upgrade to 3.21.7, 4.4.7. Exact commands for each OS are on this page.

Is CVE-2026-56317 being exploited?

CVE-2026-56317 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-56317 affect?

CVE-2026-56317 affects nuxt. Severity is medium (CVSS 6.1). 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 da

How urgent is CVE-2026-56317?

Priority 28/100. No elevated risk signals yet.

Related CVEs

CVE-2026-56326 MEDIUM 6.1 UPGRADE Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server-side open redirect vulnerability in na
CVE-2026-56301 MEDIUM 5.5 UPGRADE Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Linux, bin
CVE-2026-56698 MEDIUM 6.1 UPGRADE 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
CVE-2026-56697 MEDIUM 6.1 UPGRADE Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 accept protocol-relative paths such as //evil.com in th

References

← Back to latest CVEs