Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes

[ Description ]Official description

Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, Nuxt resolves literal or percent-encoded dot segments before rendering a page while Nitro routing, server/middleware checks, and server route rules evaluate the unresolved path. A request such as /%2e/admin can therefore render app/pages/admin.vue and its server-rendered data while checks keyed to /admin, redirects, or per-route security headers do not apply. API handlers, appMiddleware, Nuxt 3, and Nuxt 4.0.0 through 4.5.x are not affected, and exploitation requires a client that sends dot segments without browser normalization. This issue is fixed in version 4.6.3.

[ Fixes ]Fixes and patches

• nuxt 4.6.3Fixed version · GitHub Advisories · npm package nuxt: upgrade to 4.6.3 or later (affected >= 4.6.0, < 4.6.3)
• @nuxt/nitro-server 4.6.3Fixed version · GitHub Advisories · npm package @nuxt/nitro-server: upgrade to 4.6.3 or later (affected >= 4.6.0, < 4.6.3)

[ Packages ]Affected open-source packages

• nuxt npmAffected >= 4.6.0, < 4.6.3 · fixed in 4.6.3 · GHSA-9v7c-q64q-vv33
• @nuxt/nitro-server npmAffected >= 4.6.0, < 4.6.3 · fixed in 4.6.3 · GHSA-9v7c-q64q-vv33

[ References ]References

• github.com/nuxt/nuxt/commit/45463f8b58487e387149ebfb704d6a0834b3a450
• github.com/nuxt/nuxt/releases/tag/v4.6.3
• github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33