Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on
Affects nuxtSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.6.4 when convenient.
Data as of 16 Nov 2026, 15:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade nuxt and @nuxt/nitro-server and @nuxt/vite-server to 4.6.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnuxt | Affected
| Fixed in
|
| npmnuxt | Affected
| Fixed in– |
| npm@nuxt/nitro-server | Affected
| Fixed in
|
| npm@nuxt/nitro-server | Affected
| Fixed in– |
| npm@nuxt/vite-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Nuxt version 4.6.4 that fixes the issue by applying route rules to both encoded and decoded request paths. Users should upgrade to Nuxt 4.6.4 or later along with @nuxt/nitro-server and @nuxt/vite-server 4.6.4. As a workaround, server middleware can reject requests containing encoded slashes (%2F) in protected path prefixes, or a reverse proxy/CDN can be configured to reject or decode encoded slashes before forwarding requests to the application.
Description
Nuxt versions prior to 4.6.4 have a vulnerability where encoded slashes (%2F) in request paths bypass route rules protecting certain pages. This allows unauthenticated attackers to access pages behind route rules such as authentication or redirects by encoding slashes in the URL path. The issue affects catch-all routes and custom routes with multi-segment parameters. The vulnerability is fixed in Nuxt 4.6.4. Workarounds include rejecting requests with encoded slashes in server middleware or using a reverse proxy/CDN to decode or block such requests.
References
- github.com/nuxt/nuxt/security/advisories/GHSA-f3x9-2chm-73c8 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128071 (opens in a new tab)
- github.com/nuxt/nuxt/commit/084396b101e3b4d3545e86ff80dc313496bc87c0 (opens in a new tab)
- github.com/nuxt/nuxt (opens in a new tab)
- github.com/nuxt/nuxt/releases/tag/v4.6.4 (opens in a new tab)