---
id: "CVE-2026-120309"
kind: "vulnerability"
aliases: ["CVE-2026-120309"]
title: "Nuxt: encoded question mark in path lets requests read the wrong route parameter"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["h3", "node", "nuxt", "runtime", "self-hosted"]
not_affected_if: ["no-server-routes", "static-export", "version-below-4.6.0"]
published_at: "2026-11-02T03:17:28+00:00"
first_seen_at: "2026-11-02T03:31:21+00:00"
updated_at: "2026-11-02T03:31:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120309", "first_seen_at": "2026-11-02T03:31:21+00:00"}]
---

# Nuxt: encoded question mark in path lets requests read the wrong route parameter

In Nuxt 4.6.0 before 4.6.2, getRouterParam and getRouterParams can return a route parameter value different from the one h3 matched, when the request path contains an encoded question mark (%3F). An attacker can craft a request so an authorization check sees one resource while the handler loads another, reaching resources they should not access.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Nuxt version in the project's `package.json` or lockfile, e.g. `npm ls nuxt`; affected versions are `4.6.0` up to but not including `4.6.2`.
- Look for server routes that use `getRouterParam` or `getRouterParams` for an authorization decision and then load a resource through `event.context.params`.

## Fix

- Nuxt: move to `4.6.2` or later (the sources state the fix is in 4.6.2).

## Timeline

- 2026-11-02T03:31:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-120309

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_