نسخههای متأثر
بهرهبرداری
شرح آسیبپذیری
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.pathisinternal/guidefor both requests.With a repeatable catch-all (
[...slug].vue),route.params.slugis['internal/guide']instead of['internal', 'guide'], so a page that joins the segments (slug.join('/')) to load content loads the protected resource.route.pathkeeps the encoding (/docs/internal%2Fguide), so a page that loads content byroute.pathdoes not resolve it.
Not affected:
Static page routes and params that match a single segment.
/docs%2Finternaldoes not matchapp/pages/docs/internal.vue.API handlers in
server/apiandserver/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:
// 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.
پیوندها
- https://github.com/advisories/GHSA-f3x9-2chm-73c8
- https://github.com/nuxt/nuxt
- https://github.com/nuxt/nuxt/commit/084396b101e3b4d3545e86ff80dc313496bc87c0
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4
- https://github.com/nuxt/nuxt/security/advisories/GHSA-f3x9-2chm-73c8
- https://nvd.nist.gov/vuln/detail/CVE-2026-128071
گزارشدهندگان
- foudhilriahi

