Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

Nuxt: URL-handling weaknesses in navigateTo and reloadNuxtApp: SSR open redirect, client-side script execution via the open option, and protocol-relative bypass in reloadNuxtApp

CVE-2026-56326GHSA-c9cv-mq2m-ppp3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.4.7, 3.21.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nuxt

    Affected
    >= 4.0.0, < 4.4.7>= 3.5.0, < 3.21.7
    Fixed in
    4.4.7, 3.21.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:L/SA:N · score source
EPSS
  • CVE-2026-56326: 0.36% estimated exploitation activity in the next 30 days; percentile 30.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-56697: 0.34% estimated exploitation activity in the next 30 days; percentile 27.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-56698: 0.41% estimated exploitation activity in the next 30 days; percentile 35.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Three weaknesses in Nuxt's client-navigation URL handling, all reachable from documented public APIs (navigateTo and reloadNuxtApp): 1. (CVE-2026-56326) SSR open redirect in navigateTo via path-normalisation bypass. navigateTo decided whether a target was external by inspecting the raw input with hasProtocol(..., { acceptRelative: true }). Inputs such as /..//evil.com, /.//evil.com, /%2e%2e//evil.com, or /app/..//evil.com slipped past that check because they start with /, but WHATWG URL parsing then normalised them to the protocol-relative pathname //evil.com. The normalised value was written to the Location response header and into the <meta http-equiv="refresh" body of the SSR redirect page, so a victim's browser would resolve the redirect cross-origin to the attacker's host. 2. (CVE-2026-56698) Client-side script execution via navigateTo({ open: ... }). The client-side early-open handler called window.open(toPath, ...) without applying the isScriptProtocol check that gates…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-c9cv-mq2m-ppp3

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-c9cv-mq2m-ppp3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56326

Advisory: Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`
IDs: CVE-2026-56326, GHSA-c9cv-mq2m-ppp3
Record: https://patchnext.com/advisories/cve-2026-56326 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.4.7, 3.21.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.0.0, < 4.4.7; >= 3.5.0, < 3.21.7; fixed in 4.4.7, 3.21.7

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c9cv-mq2m-ppp3 (OSV record GHSA-c9cv-mq2m-ppp3 lists affected ranges: npm nuxt >=4.0.0 =3.5.0 <3.21.7 (fixed))
- Verified: https://github.com/advisories/GHSA-c9cv-mq2m-ppp3 (GitHub-reviewed advisory GHSA-c9cv-mq2m-ppp3 lists affected ranges: npm nuxt >=4.0.0 =3.5.0 <3.21.7)

Commands are suggestions: review each one before running it.

Loading voting…