CVE-2026-56326: 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

Routine

MEDIUM 6.1UPGRADE

CVE-2026-56326 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 versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server-side open redirect vulnerability in navigateTo that fails to properly validate path-normalized payloads like /..//evil.com and /.//evil.com. Attackers can bypass external-host checks using path-normalization techniques to redirect users to attacker-controlled sites via the Location header or meta-refresh, enabling phishing and OAuth authorization-code theft.

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.4% (top 70%)
CISA exploited list	No
Weakness	CWE-601
Published	2026-06-22
Last modified	2026-10-25

Publisher (CNA): VulnCheck · Vendor: nuxt

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

Am I affected?

Timeline

2026-06-22 22:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

nuxt nuxt UPGRADE

Affected: >= 3.0.0 and < 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 3.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 3.0.0 (Debian / Ubuntu)

apt-cache madison nuxt sudo apt install nuxt=<VERSION_BEFORE_3.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_3.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-56326?

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

Is CVE-2026-56326 being exploited?

CVE-2026-56326 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-56326 affect?

CVE-2026-56326 affects nuxt. Severity is medium (CVSS 6.1). Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server-side open redirect vulnerability in navigateTo that fails to properly validate path-normalized payloads like /..//evil.com and /.//evil.com. Attackers can bypass extern

How urgent is CVE-2026-56326?

Priority 29/100. No elevated risk signals yet.

References

← Back to latest CVEs