CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NCVE-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
Medium (6.5).
On this page
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.
Severity
- OWASP Top 10
- A01:2025 Broken Access Control, A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-128071 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128071?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128071?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128071 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-128071)
HTML:
<a href="https://cve.bz/cve/CVE-2026-128071"><img src="https://cve.bz/cve/badge/CVE-2026-128071.svg" alt="CVE-2026-128071"></a>
Affected
- @nuxt:nitro-server
- @nuxt:vite-server
- nuxt:nuxt
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nuxt | >= 3.0.0, < 4.6.4 |
| @nuxt nitro-server | >= 3.20.0, < 4.0.0 |
| @nuxt nitro-server | >= 4.2.0, < 4.6.4 |
| @nuxt vite-server | >= 4.6.0, < 4.6.4 |
Attack patterns (CAPEC)
- CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
- CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
- CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.