Advisory

GHSA-f3x9-2chm-73c8

Also known as: CVE-2026-128071

Summary

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

Details

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.

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 [email protected], together with @nuxt/[email protected] and @nuxt/[email protected], 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:

// 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-11-16 14:59 UTC
Modified
2026-11-16 15:15 UTC

Affected packages and fixes

nuxt

npm · All systems

Affected

  • introduced 4.0.0, fixed 4.6.4 (semver)

Fixed versions

4.6.4

Fix

nuxt

npm · All systems

Affected

  • introduced 3.0.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

@nuxt/nitro-server

npm · All systems

Affected

  • introduced 4.2.0, fixed 4.6.4 (semver)

Fixed versions

4.6.4

Fix

@nuxt/nitro-server

npm · All systems

Affected

  • introduced 3.20.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

@nuxt/vite-server

npm · All systems

Affected

  • introduced 4.6.0, fixed 4.6.4 (semver)

Fixed versions

4.6.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences