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
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.6.4
Event History
Frequently Asked Questions
Which applications are exposed to this bypass?
Applications are exposed when they use affected Nuxt packages and rely on routeRules for paths handled by a catch-all page such as app/pages/[...slug].vue or by a custom multi-segment page route. The bypass matters only if the decoded route parameter is interpreted by the page as a protected or otherwise rule-controlled path.
Does an attacker need credentials or user interaction?
No. An unauthenticated attacker can send a request containing an encoded slash (%2F) in the path, and no user interaction is required.
Which route types are not affected?
Static pages, single-segment parameter routes, server/api handlers, and server/routes handlers are not affected. They do not have the encoded-path mismatch between routeRules matching and page-route parameter decoding.
What protections can be bypassed on an affected route?
The affected request can render without routeRules configured for the decoded path, including redirects, headers, proxy behavior, SSR, noScripts, appMiddleware, and appLayout rules. The issue is fixed in version 4.6.4.