All vulnerabilities

Servers and applications

GHSA-c9cv-mq2m-ppp3

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

Severity
Medium 5.1
Published
2 Jun 2026
Last changed
2 Jun 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.21.7, 4.4.7
Weakness
Cross-site scripting (CWE-79)Open redirect (CWE-601)
Attack
Over the network · No login needed · Needs someone to click or open something
Attacker can
Read some data · Change some data
CVSS vector
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
Sources
Project advisories (GitHub)

Description

Three weaknesses in Nuxt's client-navigation URL handling, all reachable from documented public APIs (navigateTo and reloadNuxtApp):

  • 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 body of the SSR redirect page, so a victim's browser would resolve the redirect cross-origin to the attacker's host.
  • Client-side script execution via navigateTo({ open: ... }). The client-side early-open handler called window.open(toPath, ...) without applying the isScriptProtocol check that gates the normal navigateTo path. A target of javascript:...
From nuxt/nuxt's security advisory. Shortened; the full text is there.

Workarounds

  • For (1): validate redirect targets before passing them to navigateTo, for example reject any input where new URL(target, 'http://localhost').pathname starts with //, or only accept a known allow-list of paths.
  • For (2): reject any user-controlled URL whose protocol is not in an allow-list (typically just http: and https:) before passing it to navigateTo({ open: ... }).
  • For (3): same shape as (1). Reject paths starting with // (or where new URL(path, window.location.href).host !== window.location.host) before passing to reloadNuxtApp({ path }).
Workarounds as given by nuxt/nuxt's security advisory.

Affected software

SoftwareAffected versions
NuxtServers and applications · github:nuxt/nuxt
  • Every version before 3.21.7
  • From 4.0.0 before 4.4.7

About Nuxt

JavaScript framework

From Wikidata, CC0 1.0.
Developers who used it in the past year
4%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
3,404,733npm, 15 Nov 2026
GitHub stars
61,078GitHub, 15 Nov 2026
Forks
5,837GitHub, 15 Nov 2026
Latest release
v4.6.4GitHub, 15 Nov 2026
Released
2 Nov 2026GitHub
License
MIT LicenseWikidata
Written in
JavaScript, Vue.jsWikidata
First published on GitHub
26 Oct 2016GitHub

Release lines

ReleaseLatestSecurity fixes
44.6.4Yes
33.21.11Ended 31 Jul 2026
22.18.1Ended 30 Jun 2024
11.4.5Ended 21 Sept 2019

From endoflife.date.

References