---
id: "CVE-2026-119200"
kind: "vulnerability"
aliases: ["CVE-2026-119200"]
title: "Nuxt: encoded dot segments bypass route checks and expose admin pages"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["nuxt", "package", "self-hosted", "ssr", "vue"]
not_affected_if: ["api-only", "default-browser-clients", "nuxt-below-4.6.0"]
published_at: "2026-10-29T21:17:18+00:00"
first_seen_at: "2026-10-29T21:26:51+00:00"
updated_at: "2026-10-29T21:28:43+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119200", "first_seen_at": "2026-10-29T21:26:51+00:00"}]
---

# Nuxt: encoded dot segments bypass route checks and expose admin pages

From Nuxt 4.6.0 through 4.6.3, dot segments such as /%2e/admin are resolved for page rendering but not for server middleware, route rules, or security headers. An attacker can reach a page and its server-rendered data while checks keyed to /admin are skipped.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `npm ls nuxt` or check the `nuxt` version in package.json and the lockfile.
- Look for page routes that rely on server middleware, route rules, or per-route headers for access control.

## Fix

- Nuxt `4.6.3`
- Nuxt 4.0.0 through 4.5.x and API handlers and appMiddleware are not affected, per the source.

## Timeline

- 2026-10-29T21:26:51+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119200

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_