Technical impact
Nuxt, from versions 4.6.0 to 4.6.3, implements literal or percent‑encoded dot segment resolution only after a page has been rendered. Consequently a request such as /%2e/admin is interpreted as the protected /admin route by the renderer, but the Nitro server middleware, routing, redirects, and security headers that guard /admin examine the unresolved path, so none of those pre‑render checks are applied. This flaw, which correlates to CWE‑41 (Path Normalization), CWE‑436 (File/Resource Referencing) and CWE‑863 (Imprecise Input Validation), allows an attacker to force the application to serve a protected page and expose the data it renders without authorization.
Affected Systems
The vulnerability impacts Nuxt applications that rely on the Nitro server component and the Nuxt core framework. Specifically, versions 4.6.0, 4.6.1 and 4.6.2 are affected. The issue is resolved in Nuxt 4.6.3 and later releases.
Risk and Exploitability
The CVSS score of 6.5 indicates moderate severity; no EPSS score is available and the vulnerability is not listed in CISA KEV. An attacker who can submit an unnormalized request containing dot segments can bypass middleware and route checks to render unintended content. While the flaw does not provide remote code execution, it permits disclosure of protected data and circumvention of security controls.
Github GHSA