PT-2026-147001
CVE-2026-128071
·
Published
2026-11-13
·
Updated
2026-11-16
Description by
CVSS 3.1
6.5
MediumMetricsAV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Name of the Vulnerable Software and Affected Versions
Nuxt versions 3.0.0 through 4.6.3
@nuxt/nitro-server versions 3.20.0 through 4.6.3
@nuxt/vite-server versions 4.6.0 through 4.6.3
Description
An issue exists where
routeRules matching leaves an encoded slash (%2F) in the request path, while catch-all pages (such as app/pages/[...slug].vue) or custom multi-segment page routes decode it into a route parameter. This results in an incomplete getRouteRules output, allowing unauthenticated requests to render pages while bypassing configured redirect, headers, proxy, SSR, noScripts, appMiddleware, or appLayout rules for the decoded path. Protected content is only resolved if the page interprets the decoded parameter accordingly. Static pages, single-segment parameters, and server/api or server/routes handlers are not affected.Recommendations
Update Nuxt to version 4.6.4.
Update @nuxt/nitro-server to version 4.6.4.
Update @nuxt/vite-server to version 4.6.4.
Found an issue in the description? Have something to add? Feel free to write us 👾