Medium

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

  • Disclosed: 16.11.2026
  • Updated: 16.11.2026 17:17

Summary

Nuxt matches route rules against the request path with encoded slashes (%2F) left encoded, while the page router decodes them into route params. A request that spells a slash as %2F can therefore render a page through a catch-all route without the route rules configured for the path it resolves to. The fix for GHSA-6gq8-jgmh-3ffp deliberately left reserved escapes such as %2F encoded, so it did not cover this form.

Impact

An unauthenticated attacker can bypass route rules that protect paths served by a catch-all page route, or by a custom route whose param can span several segments.

ts
export default defineNuxtConfig({
  routeRules: {
    '/docs/internal/**': { appMiddleware: 'auth', headers: { 'X-Frame-Options': 'DENY' } },
    '/admin/**': { redirect: '/login' },
  },
})

With app/pages/docs/[...slug].vue, /docs/internal/guide runs auth, but /docs/internal%2Fguide renders the same page without running auth and without the header. With a root app/pages/[...slug].vue, /admin%2Fsecret is rendered instead of redirected.

The rules skipped include server-side redirect, headers, proxy, ssr and noScripts, and appMiddleware, appLayout and redirect as matched in the app during server rendering and client navigation. getRouteRules returns the same incomplete result.

Whether the page then shows protected content depends on how it reads the route:

  • With a route such as definePageMeta({ path: '/docs/:path(.*)' }), route.params.path is internal/guide for both requests.
  • With a repeatable catch-all ([...slug].vue), route.params.slug is ['internal/guide'] instead of ['internal', 'guide'], so a page that joins the segments (slug.join('/')) to load content loads the protected resource.
  • route.path keeps the encoding (/docs/internal%2Fguide), so a page that loads content by route.path does not resolve it.

Not affected:

  • Static page routes and params that match a single segment. /docs%2Finternal does not match app/pages/docs/internal.vue.
  • API handlers in server/api and server/routes. As far as we can tell, Nitro matches these against the same path as its route rules, so a handler and the rules for it agree.

Browsers send %2F in a path as written, so a plain link is enough to reach the page.

Patches

Fixed in nuxt@4.6.4, together with @nuxt/nitro-server@4.6.4 and @nuxt/vite-server@4.6.4, which it depends on. Route rules are now resolved for both the request path and the path with each %2F read as a separator, and the rules matched by either apply. Nuxt 3 has reached end of life and will not receive a fix.

Workarounds

Reject page requests whose path contains an encoded slash in a server middleware:

ts
// server/middleware/encoded-slash.ts
export default defineEventHandler((event) => {
  if (/%2f/i.test(event.path.split('?')[0])) {
    throw createError({ statusCode: 404 })
  }
})

This also rejects legitimate uses, such as an API route that takes a scoped package name (@scope%2Fname) as a param; narrow the check to the path prefixes your route rules protect if you need those.

A reverse proxy or CDN that rejects or decodes encoded slashes before forwarding the request also removes the mismatch.

Credits

Thanks to Riahi Foudhil for reporting this issue.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package nuxt >= 4.0.0, < 4.6.4, >= 3.0.0 4.6.4
npm package @nuxt/nitro-server >= 4.2.0, < 4.6.4, >= 3.20.0 4.6.4
npm package @nuxt/vite-server >= 4.6.0, < 4.6.4 4.6.4

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-436, CWE-863
Platform
npm
Package
nuxt, @nuxt/nitro-server, @nuxt/vite-server
Disclosed
16.11.2026
Updated
16.11.2026 17:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-f3x9-2chm-73c8 - CC BY 4.0

Vulnerability history: @nuxt/nitro-server

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
7
First → latest
05.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Medium 5
  • Low 2

Disclosures per year

  1. 2026: 7
  1. Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes this entry
    Medium · 6.5 CVE-2026-128071 >= 4.2.0, < 4.6.4, >= 3.20.0 4.6.4
  2. Medium · 5.3 CVE-2026-47200 >= 3.20.0, < 3.21.6, >= 4.2.0, < 4.4.6 3.21.6, 4.4.6
  3. Low · 5.4 CVE-2026-46342 >= 3.20.0, < 3.21.6, >= 4.2.0, < 4.4.6 3.21.6, 4.4.6

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.