{"id":"CVE-2026-114130","aliases":["GHSA-jjm6-p2m9-9w4x"],"title":"Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled","summary":"Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled","severity":"low","cvss":2.3,"cwe":["CWE-79"],"vendor":"nuxt","product":"nuxt","ecosystem":"npm","affected":["nuxt < 4.6.0"],"patched":["nuxt 4.6.0"],"published":"2026-10-22","updated":"2026-10-22","sourceUpdated":"2026-10-22T16:51:39Z","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-jjm6-p2m9-9w4x","references":[{"url":"https://github.com/nuxt/nuxt/security/advisories/GHSA-jjm6-p2m9-9w4x"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114130"},{"url":"https://github.com/nuxt/nuxt/pull/36459"},{"url":"https://github.com/nuxt/nuxt/commit/355ed9565127ff9b1453deb7160059ed55b3cb85"},{"url":"https://github.com/nuxt/nuxt/commit/df46569d5d3c7a7799de54c328634168fbae70bb"},{"url":"https://github.com/nuxt/nuxt/releases/tag/v4.6.0"},{"url":"https://github.com/advisories/GHSA-jjm6-p2m9-9w4x"}],"tags":["ghsa","npm","cve.org"],"cvssVector":"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","cvssSource":"cna","ingestedAt":"2026-10-21T18:09:27.275Z","epss":0.00406,"epssPercentile":0.34722,"slug":"CVE-2026-114130","body":"## Overview\n\n## Impact\n\nAn application that renders `<NuxtLink :to=\"...\">` 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.\n\nThis is an incomplete fix for [GHSA-934w-87qh-qr26](https://github.com/nuxt/nuxt/security/advisories/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.\n\nPrefixing `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.\n\nBoth `<NuxtLink custom>` and the default anchor are affected, and the `href` is present in the server-rendered HTML.\n\n## Mitigating factors\n\n- The application must have `pages` disabled (no `pages/` directory, or `pages: false`).\n- The application must bind untrusted input to `:to`.\n- A victim must click the rendered link.\n\n## Affected versions\n\n`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.\n\n## Patches\n\nFixed in `nuxt@4.6.0`. Nuxt 3 reached end of life on 31 July 2026 and will not receive a fix.\n\nAnchor `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.\n\n## Workarounds\n\nUpgrade to `nuxt@4.6.0` 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 `/`.\n\n## Affected packages\n\n- `nuxt < 4.6.0`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `nuxt 4.6.0`","depth":"sunlit","depthScore":13,"depthScoreParts":{"impact":12.6,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}