Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

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

CVE-2026-119200GHSA-9v7c-q64q-vv33

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.6.3; @nuxt/nitro-server 4.6.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-119200: 0.34% estimated exploitation activity in the next 30 days; percentile 27.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: ```ts 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-9v7c-q64q-vv33

  2. Revision 1 · created ·

    Published from ghsa record GHSA-9v7c-q64q-vv33

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-119200

Advisory: Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
IDs: CVE-2026-119200, GHSA-9v7c-q64q-vv33
Record: https://patchnext.com/advisories/cve-2026-119200 (revision 2, source checked 31 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.6.3; @nuxt/nitro-server 4.6.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.6.0, < 4.6.3; fixed in 4.6.3
- npm @nuxt/nitro-server: affected >= 4.6.0, < 4.6.3; fixed in 4.6.3

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nuxt/nitro-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt, @nuxt/nitro-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9v7c-q64q-vv33 (GitHub-reviewed advisory GHSA-9v7c-q64q-vv33 lists affected ranges: npm nuxt >=4.6.0 =4.6.0 <4.6.3)
- Verified: https://osv.dev/vulnerability/GHSA-9v7c-q64q-vv33 (OSV record GHSA-9v7c-q64q-vv33 lists affected ranges: npm nuxt >=4.6.0 =4.6.0 <4.6.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…