Skip to main content
Menu
CVEs

CVE

Nuxt route rule bypass in catch-all page routes

CVE-2026-128071EUVD-2026-125622GHSA-F3X9-2CHM-73C8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4.

Published
Last modified
Reference
Last checked
0.27% · 19th percentile
24/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Nuxt, along with the @nuxt/nitro-server and @nuxt/vite-server packages, fails to apply route rules to request paths containing an encoded slash (%2F) on catch-all pages such as [...slug].vue, because the slash is decoded into a route parameter only after the rules are matched. A remote attacker without logging in can use this to load such a page without the redirect, header, proxy, SSR, or other rules meant for the decoded path, which can expose protected content if the page uses that parameter.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Nuxt is an open-source web development framework for Vue.js. Nuxt from 3.0.0 until 4.6.4, @nuxt/nitro-server from 3.20.0 until 4.6.4, and @nuxt/vite-server from 4.6.0 until 4.6.4, routeRules matching leaves an encoded slash (%2F) in the request path while a catch-all page such as app/pages/[...slug].vue or a custom multi-segment page route decodes it into a route parameter. The getRouteRules result is therefore incomplete, and an unauthenticated request can render the page without the redirect, headers, proxy, SSR, noScripts, appMiddleware, or appLayout rules configured for the decoded path. Protected content is resolved only when the page interprets the decoded parameter accordingly: a custom multi-segment parameter can contain the decoded path, while a repeatable catch-all must join the slash-containing array element; route.path remains encoded and does not resolve that resource. Static pages, single-segment parameters, server/api handlers, and server/routes handlers are not affected because they do not have the same encoded-path mismatch. This issue is fixed in version 4.6.4.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128071 (Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128071 (entry last updated 2026-11-13):
Affected:
- nuxt nuxt: from 3.0.0, fixed in 4.6.4
- @nuxt nitro-server: from 3.20.0, fixed in 4.0.0; from 4.2.0, fixed in 4.6.4
- @nuxt vite-server: from 4.6.0, fixed in 4.6.4
Fixed versions: 4.6.4, 4.0.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128071 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128071 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nuxt/nuxt/security/advisories/GHSA-f3x9-2chm-73c8
- https://github.com/nuxt/nuxt/commit/084396b101e3b4d3545e86ff80dc313496bc87c0
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128071
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128071"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • nuxt nuxt

    From 3.0.0 · fixed in 4.6.4

  • @nuxt nitro-server

    From 3.20.0 · fixed in 4.0.0; From 4.2.0 · fixed in 4.6.4

  • @nuxt vite-server

    From 4.6.0 · fixed in 4.6.4

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128071

Is CVE-2026-128071 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-128071?

nuxt: from 3.0.0 before 4.6.4. nitro-server: from 3.20.0 before 4.0.0; from 4.2.0 before 4.6.4. vite-server: from 4.6.0 before 4.6.4.Source: cve.now feed data

How do I fix CVE-2026-128071?

Upgrade to a fixed version: nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4.Source: cve.now feed data