GitHub Advisoryadvisory · npm
GHSA-jjm6-p2m9-9w4x Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled
LOW
Official page ↗
- Aliases
- CVE-2026-114130
- Ecosystem
- npm
- Packages
- nuxt
- Severity
- Low
- CVSS vector
- 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
- Weaknesses
- CWE-79
- Reviewed
- 2026-10-22
Affected packages
• npm nuxt: < 4.6.0 → fixed in 4.6.0
Description
Impact
An application that renders `` with a value it does not control can be made to render an anchor whose `href` executes script in the application's origin when clicked.
This is an incomplete fix for GHSA-934w-87qh-qr26 (CVE-2026-53722). It only affects applications running without a `pages/` directory, where `pages` resolves to `false` and Nuxt registers its own router in place of vue-router. Applications using vue-router are not affected.
Prefixing `javascript:` with an ASCII C0 control character, for example `%01`, meant the value was not recognised as having a protocol. It was classified as an internal route and so never reached the protocol check added in GHSA-934w-87qh-qr26, and the router used for `pages: false` passed it through to the rendered `href` unchanged. Browsers strip the leading control character and run the result as a script URL.
Both `` and the default anchor are affected, and the `href` is present in the server-rendered HTML.
Mitigating factors
• The application must have `pages` disabled (no `pages/` directory, or `pages: false`).
• The application must bind untrusted input to `:to`.
• A victim must click the rendered link.
Affected versions
`nuxt` `<4.6.0`, including all Nuxt 3 releases. Versions before `4.4.7` and `3.21.7` are also affected by GHSA-934w-87qh-qr26.
Patches
Fixed in `[email protected]`. Nuxt 3 reached end of life on 31 July 2026 and will not receive a fix.
Anchor `href` values are now checked for script-capable protocols wherever they are rendered, including the router used when `pages` is disabled. Protocol detection also moved to the platform `URL` parser, so a URL is classified the same way the browser will read it.
Workarounds
Upgrade to `[email protected]` or later. If you cannot upgrade, including on Nuxt 3, validate values before binding them to `:to`, for example by rejecting anything that is not a path beginning with a single `/`.
Related
Alias · CVE (1)
- CVE-2026-114130 Nuxt is an open-source web development framework for Vue.js. vulnerability
Weakness · CWE (1)
- CWE-79 Improper Neutralization of Input During Web Page Generation weakness
References
- https://github.com/nuxt/nuxt/security/advisories/GHSA-jjm6-p2m9-9w4x web
- https://nvd.nist.gov/vuln/detail/CVE-2026-114130 advisory
- https://github.com/nuxt/nuxt/pull/36459 web
- https://github.com/nuxt/nuxt/commit/355ed9565127ff9b1453deb7160059ed55b3cb85 web
- https://github.com/nuxt/nuxt/commit/df46569d5d3c7a7799de54c328634168fbae70bb web
- https://github.com/nuxt/nuxt package
- https://github.com/nuxt/nuxt/releases/tag/v4.6.0 web