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

published 2026-10-29 10 d ago modified 2026-11-04 5 d ago also GHSA-9v7c-q64q-vv33 , EUVD-2026-113371

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 links 2

npm nuxt 4.6.3
npm @nuxt/nitro-server 4.6.3

github.com/nuxt/nuxt@45463f8 commit
github.com/nuxt/nuxt/releases/tag/v4.6.3 release

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 5 d ago (2026-11-04)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	nuxt	>=4.6.0, <4.6.3	4.6.3
npm	@nuxt/nitro-server	>=4.6.0, <4.6.3	4.6.3

Affected products

nuxt nuxt
@nuxt nitro-server

Classification

Weakness

CWE-41 Improper Resolution of Path Equivalence
CWE-436 Interpretation Conflict
CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary