Nuxt 4.6.0 before 4.6.2 Route Param Confusion via getRouterParam
Only affects Nuxt 4.6.0 before 4.6.2 apps that read the same route param from two sources and rely on them agreeing. Fixed in Nuxt 4.6.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.6.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 4.6.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Nuxt versions from 4.6.0 up to (but not including) 4.6.2 are affected. An attacker can send a crafted request with an encoded question mark in the path so that a route parameter read by Nuxt's getRouterParam or getRouterParams helpers differs from the one h3 matched, which can let them bypass authorization checks and access resources they should not be able to reach.
Read the original 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.
What to do
Upgrade to a fixed version: 4.6.2.
Workaround: Read a route param from a single source for both the check and the lookup.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nuxt nuxt
From 4.6.0 · fixed in 4.6.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120309
What does this mean?
When a path segment contains an encoded question mark (%3F), a request can pass an authorization check for one resource and then act on a different resource, which gives access to resources it should not reach.Source: github.com
Am I affected, and how do I check?
Affected versions are Nuxt 4.6.0 up to but not including 4.6.2, in the nuxt and @nuxt/nitro-server packages. The setup also needs code that reads the same route param from two sources, such as the Nuxt helper and event.context.params, and relies on them agreeing. To check, look at the nuxt version in package.json or the lockfile, and search the code for places that read the same route param in two ways.Source: github.com
What should I do about it?
Upgrade nuxt to 4.6.2 or later. Until then, read each route param from a single source for both the check and the lookup.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data