CVEvulnerability

CVE-2026-119200

6.5 MEDIUM EPSS 0.34% Published 2026-10-29 Modified 2026-10-30 Official page ↗

Exploitation and prioritisation

EPSS
0.34% chance of exploitation in the next 30 days · in the top 72.6% of all CVEs (2026-11-03)
EU Vulnerability Database
EUVD-2026-113371

Affected packages

EcosystemPackageVulnerableFixed inAdvisory
npm@nuxt/nitro-server>= 4.6.0, < 4.6.34.6.3GHSA-9v7c-q64q-vv33
npmnuxt>= 4.6.0, < 4.6.34.6.3GHSA-9v7c-q64q-vv33
Status
Awaiting Analysis
Published
2026-10-29
Last modified
2026-10-30
Assigner
[email protected]
CVSS 3.1 ([email protected])
6.5 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-41, CWE-436, CWE-863

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.

Related

Weakness · CWE (3)

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

Referenced by GitHub Advisory · alias (1)

  • GHSA-9v7c-q64q-vv33 Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes advisory · npm

References