# CVE-2026-128071: Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DHI-7kua-6y74-7m5b-w5dk, GHSA-f3x9-2chm-73c8

## What is CVE-2026-128071?

CVE-2026-128071 is a medium-severity vulnerability in @nuxt nitro-server, published on 13 Nov 2026. 

### Official description

Nuxt is an open-source web development framework for Vue.js. Nuxt from 3.0.0 until 4.6.4, @nuxt/nitro-server from 3.20.0 until 4.6.4, and @nuxt/vite-server from 4.6.0 until 4.6.4, routeRules matching leaves an encoded slash (%2F) in the request path while a catch-all page such as app/pages/[...slug].vue or a custom multi-segment page route decodes it into a route parameter. The getRouteRules result is therefore incomplete, and an unauthenticated request can render the page without the redirect, headers, proxy, SSR, noScripts, appMiddleware, or appLayout rules configured for the decoded path. Protected content is resolved only when the page interprets the decoded parameter accordingly: a custom multi-segment parameter can contain the decoded path, while a repeatable catch-all must join the slash-containing array element; route.path remains encoded and does not resolve that resource. Static pages, single-segment parameters, server/api handlers, and server/routes handlers are not affected because they do not have the same encoded-path mismatch. This issue is fixed in version 4.6.4.

Weakness: CWE-863 (Incorrect Authorization), CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2026-128071?

5 open source packages ship an affected version, including @nuxt/nitro-server, @nuxt/vite-server and nuxt.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `@nuxt/nitro-server` | npm | `pkg:npm/%40nuxt/nitro-server` | From 3.20.0 | None |
| `@nuxt/nitro-server` | npm | `pkg:npm/%40nuxt/nitro-server` | From 4.2.0 | 4.6.4 |
| `@nuxt/vite-server` | npm | `pkg:npm/%40nuxt/vite-server` | From 4.6.0 | 4.6.4 |
| `nuxt` | npm | `pkg:npm/nuxt` | From 3.0.0 | None |
| `nuxt` | npm | `pkg:npm/nuxt` | From 4.0.0 | 4.6.4 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@nuxt/nitro-server`, `@nuxt/vite-server`, `nuxt` | 4.6.4 |

## How do I fix CVE-2026-128071?

Upgrade @nuxt/nitro-server to 4.6.4 or later.

## Is CVE-2026-128071 being exploited?

There is no known exploitation of CVE-2026-128071 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128071 and fix it if it is affected.

What it is: CVE-2026-128071 is a medium-severity vulnerability in @nuxt nitro-server, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128071 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/nitro-server (npm): affected from 3.20.0; no fix listed
- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.6.4
- @nuxt/vite-server (npm): affected from 4.6.0; fixed in 4.6.4
- nuxt (npm): affected from 3.0.0; no fix listed
- nuxt (npm): affected from 4.0.0; fixed in 4.6.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128071/ (Markdown: https://insights.sbomify.com/CVE-2026-128071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128071
- OSV: https://osv.dev/vulnerability/CVE-2026-128071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128071/
Summaries are generated and may contain mistakes; the official description above is the record.
