Answer in brief
CVE-2026-119200 records a Medium severity (CVSS 6.5) vulnerability in Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes. The current sources do not mark it as known exploited. The current feed maps @nuxt/nitro-server (generic), nuxt/nuxt (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @nuxt/nitro-server (generic), nuxt/nuxt (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @nuxt/nitro-servergeneric | >=4.6.0 <4.6.3 | 4.6.3 |
| nuxt/nuxtgeneric | >=4.6.0 <4.6.3 | 4.6.3 |
Published upstream
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 29, 2026
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.
Quoted source text, attributed separately from HOL analysis.