Interpretation Conflict Affecting @nuxt/nitro-server package, versions >=4.6.0 <4.6.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-NUXTNITROSERVER-22132590
- published2 Nov 2026
- disclosed2 Nov 2026
- creditseslo82
Introduced: 2 Nov 2026
NewCVE-2026-120309 (opens in a new tab)How to fix?
Upgrade @nuxt/nitro-server to version 4.6.2 or higher.
Overview
@nuxt/nitro-server is a Nitro server integration for Nuxt
Affected versions of this package are vulnerable to Interpretation Conflict via getRouterParam and getRouterParams in nuxt/server, which misalign the raw request URL against the decoded path h3 routed on when a path segment contains an encoded question mark (%3F). Because h3 routes only up to the decoded ? but the raw URL is not cut at the same point, the helpers read parameters from the wrong path segments and can return a value different from the one h3 matched in event.context.params. An attacker can craft a request where an authorization check using the Nuxt helper passes for one resource while the actual resource selection, driven by event.context.params or h3's matched params, operates on a different resource, enabling access to unauthorized resources.
Note: This is only exploitable when an application reads the same route parameter from two different sources - one being getRouterParam/getRouterParams and the other being event.context.params or h3's helpers - and relies on them agreeing.
Workaround
Upgrade to nuxt@4.6.2. If upgrading is not possible: read a route parameter from a single source for both the authorization check and the resource lookup, or reject requests whose path contains %3F in a server middleware.