NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

mediumCVSS 3.1 6.5GHSA-9v7c-q64q-vv33

Nuxt 4.6.0 to 4.6.2 resolves `.` and `..` path segments, including `%2e` forms, before rendering a page, but Nitro middleware and route rules see the raw path. A request to `/%2e/admin` renders `/admin` and skips checks on `/admin`. An unauthenticated client can use this. Upgrade `nuxt` to 4.6.3.

Published Oct 30, 2026 · Analysis Oct 31, 2026

What an attacker can do

Since 4.6.0, Nuxt normalizes the request path before the page router renders it. Nitro's routing, route rules and server/middleware still see the path with dot segments in place. A request for /%2e/admin is rendered as the page at /admin, but a middleware that tests event.path.startsWith('/admin') sees /./admin and lets it pass. The same holds for /.%2e/admin and /x/%2e%2e/admin. The page renders together with the data it fetches during server rendering (CWE-41, CWE-436, CWE-863).

Server-side redirect and headers route rules are skipped the same way. A rule such as '/admin/**': { redirect: '/login' } does not redirect /%2e/admin/secret, and per-route headers like Content-Security-Policy are not sent.

Not affected: API handlers in server/api and server/routes, because Nitro's router does not resolve dot segments, and appMiddleware route rules and definePageMeta middleware, which match the resolved route. Nuxt 3.x and 4.0.0 to 4.5.x pass the path to the page router unchanged, so those requests return 404. Browsers resolve dot segments before sending, so the attacker needs a client such as curl that sends the path as written.

Who is affected

nuxt and @nuxt/nitro-server from 4.6.0 up to but not including 4.6.3. Exposure needs page routes whose access control or headers rely on server/middleware path checks or on server-side redirect and headers route rules. Check versions:

npm ls nuxt @nuxt/nitro-server

Then grep server/middleware for event.path or event.node.req.url checks, and nuxt.config for route rules.

nuxt

Ecosystem
npm
Affected
>= 4.6.0, < 4.6.3
Fixed in
4.6.3
Check
npm ls nuxt

@nuxt/nitro-server

Ecosystem
npm
Affected
>= 4.6.0, < 4.6.3
Fixed in
4.6.3
Check
npm ls @nuxt/nitro-server

How to fix it

Upgrade to nuxt 4.6.3, which carries @nuxt/nitro-server 4.6.3:

npm install [email protected]

A page request whose path has . or .. segments now gets a 404. Route-rule keys and lookup paths have their dot segments resolved, percent-encoded forms included, before comparison.

Workaround: add a server middleware that runs before your others (they run in file name order), for example server/middleware/0.dot-segments.ts. It throws a 404 when event.path without the query contains a . or .. segment. Checking getRequestURL(event).pathname is not enough, because it keeps percent-encoding such as %61 that the page router decodes. Path checks should also allow for case-insensitive page routing unless router.options.sensitive is set. A reverse proxy or CDN that normalizes paths before forwarding also removes the mismatch.

How to tell if you were hit

Search access logs for page requests whose path contains /./, /../, %2e or %2E segments, such as /%2e/admin. Browsers never send those, so a hit means a scripted client. Compare any 200 responses with the protected routes you expect to return 401 or a redirect. Check for protected pages served without the headers you configured.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

Since 4.6.0, Nuxt resolves . and .. segments in the request path, including percent-encoded forms such as %2e, before rendering a page. Nitro's routing, Nitro's route rules and server/middleware see the path with those segments still in place. A request for /%2e/admin therefore renders the page at /admin, while server-side checks keyed on /admin do not apply.

Impact

An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.

server/middleware that checks event.path (or event.node.req.url) is skipped:

export default defineEventHandler((event) => {
  if (event.path.startsWith('/admin') && !isAuthenticated(event)) {
    throw createError({ statusCode: 401 })
  }
})

With this middleware, /admin returns 401, but /%2e/admin, /.%2e/admin and /x/%2e%2e/admin reach the middleware with event.path set to /./admin, /../admin and /x/../admin, and render app/pages/admin.vue along with the data it fetches during server rendering.

Server-side redirect and headers route rules are skipped in the same way, so '/admin/**': { redirect: '/login' } does not redirect /%2e/admin/secret, and per-route security headers such as Content-Security-Policy are not sent.

Not affected:

  • API handlers in server/api and server/routes. Nitro's router does not resolve dot segments, so these requests do not reach the handler.
  • appMiddleware route rules and middleware declared with definePageMeta, which are matched against the resolved route.
  • Nuxt 3.x and 4.0.0 to 4.5.x, which pass the path to the page router unchanged, so these requests 404.

Browsers resolve dot segments before sending a request, so exploitation requires a client that sends the path as written.

Patches

Fixed in [email protected] and @nuxt/[email protected]. A page request whose path contains . or .. segments now receives a 404 instead of rendering the page the path resolves to, and route-rule keys and lookup paths have their dot segments resolved, including percent-encoded spellings, before they are compared.

Workarounds

Reject dot segments in a server middleware that runs before your other middleware (middleware runs in file name order):

// server/middleware/0.dot-segments.ts
export default defineEventHandler((event) => {
  if (/(?:^|\/)\.{1,2}(?:\/|$)/.test(event.path.split('?')[0])) {
    throw createError({ statusCode: 404 })
  }
})

Checking getRequestURL(event).pathname instead of event.path is not a sufficient workaround: it resolves dot segments, but keeps percent-encoding such as %61 that the page router decodes. Path checks in server middleware should also account for the page router matching paths case-insensitively unless router.options.sensitive is set.

A reverse proxy or CDN that normalises the request path before forwarding it also removes the mismatch.

Credits

Thanks to @vinzabe, @nikhilagrawalsf (Nikhil Agrawal, Mettle Labs), @0xjunwei and @kq5y, who reported this issue independently.

Credited to vinzabe, nikhilagrawalsf, 0xjunwei, kq5y.

Questions

Are Nuxt 3 and Nuxt 4.5 affected by CVE-2026-119200?

No. Nuxt 3.x and 4.0.0 to 4.5.x pass the path to the page router unchanged, so dot-segment requests return 404. The affected range is 4.6.0 to 4.6.2.

Do my server/api routes need a fix?

No. Nitro's router does not resolve dot segments, so such requests do not reach handlers in server/api and server/routes. Page routes guarded by server middleware or route rules are the exposure.

Can a browser trigger this?

Not by itself, because browsers resolve dot segments before sending a request. The attacker needs a client that sends the path as written, such as curl.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More npm vulnerabilities

All npm entries