
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-128071 is a route rule bypass vulnerability in the Nuxt web development framework for Vue.js, caused by an interpretation conflict between how route rules match encoded slashes (%2F) and how catch-all page routes decode them into route parameters. It affects Nuxt versions 3.0.0 through 4.6.4, @nuxt/nitro-server versions 3.20.0–4.0.0 and 4.2.0–4.6.4, and @nuxt/vite-server versions 4.6.0–4.6.4. The vulnerability was published on November 13, 2026, and is described as an incomplete fix for a prior advisory (GHSA-6gq8-jgmh-3ffp). It carries a CVSS v3.1 base score of 6.5 (Medium) (GitHub Advisory, Feedly).
The root cause is an interpretation conflict (CWE-436) combined with incorrect authorization (CWE-863): Nuxt's getRouteRules / matchRouteRules functions match route rules against the raw request path, leaving %2F encoded, while catch-all page routes (e.g., app/pages/[...slug].vue) and custom multi-segment routes decode %2F into a literal / within route parameters. This mismatch means that a request to /admin%2Fsecret is not matched against the /admin/** route rule, so configured protections (redirects, appMiddleware, headers, proxy, SSR, noScripts, appLayout) are silently skipped. The attack requires no authentication, no user interaction, and is exploitable over the network with low complexity. Static pages, single-segment parameters, and server/api or server/routes handlers are not affected because they do not exhibit the same encoded-path mismatch (GitHub Advisory, Fix Commit).
An unauthenticated attacker can bypass route-level security controls — including authentication middleware, redirect rules, security headers (e.g., X-Frame-Options), proxy rules, and SSR restrictions — on any path served by a catch-all or multi-segment page route. Whether protected content is actually exposed depends on how the page reads its route parameter: pages that join catch-all slug segments or use a multi-segment custom parameter will resolve and render the protected resource, while pages relying on route.path (which remains encoded) will not. The impact is rated as low confidentiality and low integrity loss with no availability impact, but in practice this can expose sensitive content or allow security control bypass without any credentials (GitHub Advisory).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the disclosure date. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. However, exploitation is trivially simple — a standard browser or HTTP client can trigger the bypass by encoding a slash as %2F in the URL path, requiring no special tools or privileges (GitHub Advisory, Feedly).
routeRules to protect paths served by catch-all pages (e.g., [...slug].vue) or custom multi-segment routes. Look for paths with configured appMiddleware, redirect, or security headers./admin/** (redirect to /login) or /docs/internal/** (auth middleware)./ separators in the protected path with %2F. For example, instead of requesting /admin/secret, request /admin%2Fsecret, or instead of /docs/internal/guide, request /docs/internal%2Fguide.curl: curl https://target.example.com/admin%2Fsecret. Browsers send %2F in the path as written, so a plain hyperlink is sufficient./admin%2Fsecret), finds no matching rule for /admin/**, and renders the catch-all page without applying the redirect, auth middleware, or security headers.slug.join('/')) or uses a multi-segment parameter, it resolves and renders the protected resource, exposing content that should have been gated (GitHub Advisory).%2F or %2f (encoded slash) in place of a path separator (e.g., /admin%2Fsecret, /docs/internal%2Fguide).%2F in the path portion (not query string) that return HTTP 200 responses for paths that should return 301/302 redirects or 401/403 responses.X-Frame-Options, custom x-* headers) on responses to paths containing %2F, or absence of redirect responses for paths that should trigger redirect route rules.Upgrade to Nuxt 4.6.4 (along with @nuxt/nitro-server@4.6.4 and @nuxt/vite-server@4.6.4), which resolves route rules for both the raw encoded path and the path with %2F decoded as a separator. Note that Nuxt 3 has reached end of life and will not receive a fix. As a temporary workaround, add a server middleware to reject requests containing encoded slashes in the path:
// server/middleware/encoded-slash.ts
export default defineEventHandler((event) => {
if (/%2f/i.test(event.path.split('?')[0])) {
throw createError({ statusCode: 404 })
}
})Alternatively, configure a reverse proxy or CDN to reject or decode encoded slashes before forwarding requests. Narrow the middleware check to specific path prefixes if legitimate uses of %2F (e.g., scoped npm package names) must be preserved (GitHub Advisory, Nuxt v4.6.4 Release).
The vulnerability was reported by security researcher Riahi Foudhil and published by Nuxt maintainer Daniel Roe as part of a broader security release (v4.6.4) that addressed eight advisories in Nuxt and three more in Nitro. The release notes explicitly recommend upgrading as soon as possible and describe this as a security release (Nuxt v4.6.4 Release, GitHub Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."