Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a javascript: URL prefixed with an ASCII control character executes from when pages is disabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · 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 · score source

EPSS

• CVE-2026-114130: 0.41% estimated exploitation activity in the next 30 days; percentile 34.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact An 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. 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 <NuxtLink custom and the default anchor are affected, and the href is present in the server-rendered HTML. Mitigating factors…

Published by the source

22 Oct 2026, 16:51 UTC

Last modified by the source

22 Oct 2026, 17:00 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 5 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jjm6-p2m9-9w4x

2. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jjm6-p2m9-9w4x

3. Revision 3 · amended · 24 Oct 2026

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

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-jjm6-p2m9-9w4x

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-jjm6-p2m9-9w4x

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

# Patch Next advisory brief: CVE-2026-114130

Advisory: Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from ` ` when `pages` is disabled
IDs: CVE-2026-114130, GHSA-jjm6-p2m9-9w4x
Record: https://patchnext.com/advisories/cve-2026-114130 (revision 5, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected < 4.6.0; fixed in 4.6.0

## 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://github.com/advisories/GHSA-jjm6-p2m9-9w4x (GitHub-reviewed advisory GHSA-jjm6-p2m9-9w4x lists affected ranges: npm nuxt >=0 <4.6.0)
- Verified: https://osv.dev/vulnerability/GHSA-jjm6-p2m9-9w4x (OSV record GHSA-jjm6-p2m9-9w4x lists affected ranges: npm nuxt >=0 <4.6.0 (fixed))

Commands are suggestions: review each one before running it.