# CVE-2026-114130: 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 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-jjm6-p2m9-9w4x

## What is CVE-2026-114130?

CVE-2026-114130 is a low-severity vulnerability in nuxt, published on 21 Oct 2026. 

### Official description

Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.0, an incomplete fix for CVE-2026-53722 allows an application with pages disabled to render a script-capable URL through NuxtLink when attacker-controlled input bound to to is prefixed with an ASCII C0 control character. The no-pages router classifies the value as an internal route before the earlier protocol check and passes it to the rendered anchor href; browsers remove the leading control character and interpret the remaining javascript: URL. The default anchor and NuxtLink custom output are affected, the unsafe href is present in server-rendered HTML, and a victim must click the link for script to execute in the application's origin. This issue is fixed in version 4.6.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-114130?

2 open source packages ship an affected version, including nuxt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | All versions | 4.6.0 |
| `nuxt` | npm | All versions | 4.6.0 |

## How do I fix CVE-2026-114130?

Upgrade nuxt to 4.6.0 or later.

## Is CVE-2026-114130 being exploited?

There is no known exploitation of CVE-2026-114130 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114130 and fix it if it is affected.

What it is: CVE-2026-114130 is a low-severity vulnerability in nuxt, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114130 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected all versions; fixed in 4.6.0
- nuxt (npm): affected all versions; fixed in 4.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114130/ (Markdown: https://insights.sbomify.com/CVE-2026-114130/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114130
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114130
- OSV: https://osv.dev/vulnerability/CVE-2026-114130

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114130/
Summaries are generated and may contain mistakes; the official description above is the record.