CVE-2026-120309

Nuxt 4.6.0 before 4.6.2 Route Param Confusion via getRouterParam

Published Nov 2, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Nuxt from 4.6.0 before 4.6.2 contains a route parameter confusion vulnerability in getRouterParam and getRouterParams that lets attackers return a parameter value different from the one h3 matched by sending paths containing an encoded question mark (%3F). Attackers can craft requests where authorization checks use the Nuxt helper value while resource selection uses event.context.params, allowing access to unauthorized resources.

Analysis

AI-generated

Technical impact

Nuxt versions 4.6.0 through 4.6.1 contain a route parameter confusion flaw in the getRouterParam and getRouterParams helper functions. By encoding a question mark (%3F) inside a path component, an attacker can cause the framework to return a different value when the parameter is accessed through the helper than when it is retrieved from the routing context. If an application authorises a request by comparing the helper value to a known credential but selects resources using event.context.params, the mismatch enables the attacker to bypass access checks and retrieve data that should be restricted.

Affected Systems

The target is the Nuxt framework itself. Versions 4.6.0, 4.6.1, and any intermediate builds prior to the release of 4.6.2 are affected. Projects built with these releases that rely on getRouterParam for authentication or authorization should be considered at risk. The vulnerability is present in the core Nuxt package and its Nitro server component.

Risk and Exploitability

The CVSS base score of 6.3 places this flaw in the medium severity range. EPSS data is not listed, and the vulnerability is not yet catalogued in CISA's KEV database, suggesting that active exploitation is not known. However, because the flaw can be triggered by a crafted HTTP request containing an encoded question mark, any public‑facing Nuxt application could be vulnerable. Attackers need only send a malicious URL and may be able to read or modify protected resources without additional privileges. Organizations running affected versions should consider the risk moderate to high.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Nuxt to a fixed version such as 4.6.2 or later.
  • Audit authorization logic to ensure it references event.context.params consistently rather than the helper value, and adjust checks accordingly.
  • Implement input validation or route filtering to reject encoded question marks (%3F) in path segments unless explicitly required.

Generated by OpenCVE AI on November 2, 2026 at 03:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Nuxt nuxt/nitro-server
Vendors & Products Nuxt nuxt/nitro-server
Type Values Removed Values Added
Description Nuxt from 4.6.0 before 4.6.2 contains a route parameter confusion vulnerability in getRouterParam and getRouterParams that lets attackers return a parameter value different from the one h3 matched by sending paths containing an encoded question mark (%3F). Attackers can craft requests where authorization checks use the Nuxt helper value while resource selection uses event.context.params, allowing access to unauthorized resources.
Title Nuxt 4.6.0 before 4.6.2 Route Param Confusion via getRouterParam
First Time appeared Nuxt
Nuxt nuxt
Nuxt nuxt\/nitro-server
Weaknesses CWE-436
CPEs cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:*
cpe:2.3:a:nuxt:nuxt\/nitro-server:*:*:*:*:*:*:*:*
Vendors & Products Nuxt
Nuxt nuxt
Nuxt nuxt\/nitro-server
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 2, 2026, 2:21 PM
Reserved
Nov 1, 2026, 12:48 PM
Status
Awaiting Analysis
Published
Nov 2, 2026, 3:17 AM
Modified
Nov 2, 2026, 7:34 PM