- Severity: MEDIUM
- CVE: CVE-2026-128077
- Ecosystems: npm
- Packages: @nuxt/nitro-server
### Summary
Since `4.6.0`, Nuxt parses a request path that starts with `//` as a URL with a host before rendering a page, so `//x/admin` renders the page at `/admin`. Nitro’s routing, Nitro’s route rules and `server/middleware` see the path as `//x/admin`, so server-side checks keyed on `/admin` do not apply. The fix for [GHSA-9v7c-q64q-vv33](https://github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33) in `4.6.3` covered dot segments but not this form.
### Impact
An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.
A route-scoped server handler is skipped:
“`ts
// nuxt.config.ts
export default defineNuxtConfig({
serverHandlers: [{ route: ‘/admin’, middleware: true, handler: ‘~~/server/admin-guard.ts’ }],
})
“`
“`ts
// server/admin-guard.ts
export default defineEventHandler((event) => {
if (!isAuthenticated(event)) {
throw createError({ statusCode: 401 })
}
})
“`
With this handler, `/admin` returns 401, but `//x/admin` and `///x/admin` render `app/pages/admin.vue` along with the data it fetches during server rendering. `server/middleware` that checks `event.path.startsWith(‘/admin’)` is skipped in the same way.
Server-side `redirect` and `headers` route rules are also skipped, so `’/admin/**’: { redirect: ‘/login’ }` does not redirect `//x/admin/secret`, and per-route security headers such as `Content-Security-Policy` are not sent.
Browsers send a path such as `//x/admin` as written, so a plain li…
Source: GitHub Security Advisories · 2026-11-13