CVE-2026-114130

Awaiting Analysis Awaiting Analysis - Queue

JavaScript URL Execution in Nuxt Framework

Publication date: 2026-10-21

Last updated on: 2026-10-28

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-21

Last Modified

2026-10-28

Generated

2026-11-10

AI Q&A

2026-10-22

EPSS Evaluated

2026-11-09

NVD

CVE-2026-114130

EUVD

EUVD-2026-107413

Affected Vendors & Products

Vendor	Product	Version / Range
nuxt	nuxt	< 4.6.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-79	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

Executive Summary

This vulnerability affects Nuxt.js versions before 4.6.0. It allows an attacker to execute JavaScript URLs through NuxtLink components when the pages feature is disabled. The issue occurs when an attacker prefixes a javascript: URL with an ASCII control character (like %01). Browsers strip the control character and execute the script, leading to potential cross-site scripting (XSS) attacks. The vulnerability only affects applications without a pages/ directory or with pages set to false.

Detection Guidance

To detect this vulnerability, check if your Nuxt.js application is running a version prior to 4.6.0. Use commands like 'npm list nuxt' or 'yarn list nuxt' to verify the installed version. Inspect server-rendered HTML for NuxtLink components with javascript: URLs, especially those with unusual prefixes.

Impact Analysis

An attacker could trick users into clicking a malicious link that executes arbitrary JavaScript in the context of your application. This could lead to data theft, session hijacking, or other malicious activities. The impact is limited to applications using Nuxt.js versions before 4.6.0 with pages disabled and untrusted input bound to the :to prop.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality principles or HIPAA's security requirements for protected health information. Organizations using affected Nuxt.js versions may face compliance risks if exploited.

Mitigation Strategies

Upgrade Nuxt.js to version 4.6.0 or later immediately. If upgrading is not possible, validate all input bound to the :to prop in NuxtLink components to reject non-path values. Disable pages feature if not needed or ensure proper protocol checks are in place.

Hi! I’m here to help you understand CVE-2026-114130. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...