Read the docs

Encoded slash bypasses Nuxt route rules on catch-all pages

Priority LOW 28CWE-436Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-863.

Summary

Nuxt from 3.0.0 before 4.6.4, @nuxt/nitro-server from 3.20.0 before 4.0.0 and from 4.2.0 before 4.6.4, and @nuxt/vite-server from 4.6.0 before 4.6.4 are affected. Route rule matching misses an encoded slash (%2F) in the request path that a catch-all page decodes, so rules for the decoded path do not apply (CWE-436). An unauthenticated remote attacker can render such a page without its redirect, header, proxy or middleware rules.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

EPSS 0.00268 19th percentileScored 2026-11-16
Fix Fixed nuxt (nuxt): 4.6.4nitro-server (@nuxt): 4.0.0, 4.6.4+4 more products

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
nuxtnuxt3.0.0 to before 4.6.44.6.4Patch availableCNA
nuxtnitro-server3.20.0 to before 4.0.0; 4.2.0 to before 4.6.44.0.0, 4.6.4Patch availableCNA
nuxtvite-server4.6.0 to before 4.6.44.6.4Patch availableCNA
—nuxt (npm)4.0.0 to before 4.6.44.6.4Patch availableGHSA-f3x9-2chm-73c8
—nuxt (npm)3.0.0 and later—No fix listedGHSA-f3x9-2chm-73c8
—@nuxt/nitro-server (npm)4.2.0 to before 4.6.44.6.4Patch availableGHSA-f3x9-2chm-73c8
—@nuxt/nitro-server (npm)3.20.0 and later—No fix listedGHSA-f3x9-2chm-73c8
—@nuxt/vite-server (npm)4.6.0 to before 4.6.44.6.4Patch availableGHSA-f3x9-2chm-73c8
  • nuxt Vendornuxt Affected 3.0.0 to before 4.6.4 Fixed in 4.6.4 Patch available CNA
  • nitro-server Vendornuxt Affected 3.20.0 to before 4.0.0; 4.2.0 to before 4.6.4 Fixed in 4.0.0, 4.6.4 Patch available CNA
  • vite-server Vendornuxt Affected 4.6.0 to before 4.6.4 Fixed in 4.6.4 Patch available CNA
  • nuxt (npm) Vendor— Affected 4.0.0 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-f3x9-2chm-73c8
  • nuxt (npm) Vendor— Affected 3.0.0 and later Fixed in — No fix listed GHSA-f3x9-2chm-73c8
  • @nuxt/nitro-server (npm) Vendor— Affected 4.2.0 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-f3x9-2chm-73c8
  • @nuxt/nitro-server (npm) Vendor— Affected 3.20.0 and later Fixed in — No fix listed GHSA-f3x9-2chm-73c8
  • @nuxt/vite-server (npm) Vendor— Affected 4.6.0 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-f3x9-2chm-73c8

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:*——nuxt
  • cpe:2.3:a:nuxt:nuxt:*:*:*:*:*:*:*:* Versions — — ·nuxt

Remediation

Update nuxt and @nuxt/vite-server to 4.6.4, and update @nuxt/nitro-server to 4.0.0 or 4.6.4. The sources list no fixed version for nuxt. The sources list no fixed version for @nuxt/nitro-server.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA nuxt (nuxt) Fixed in 4.6.4
  • Fix · CNA nitro-server (@nuxt) Fixed in 4.0.0, 4.6.4
  • Fix · CNA vite-server (@nuxt) Fixed in 4.6.4
  • Fix · GHSA-f3x9-2chm-73c8 nuxt (npm) Fixed in 4.6.4 Advisory →
  • Fix · GHSA-f3x9-2chm-73c8 @nuxt/nitro-server (npm) Fixed in 4.6.4 Advisory →
  • Fix · GHSA-f3x9-2chm-73c8 @nuxt/vite-server (npm) Fixed in 4.6.4 Advisory →

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-128071
  2. 2026-11-16 Alias added: GHSA-f3x9-2chm-73c8
  3. 2026-11-16 Fix available: npm/@nuxt/[email protected], npm/@nuxt/[email protected], npm/[email protected] · GHSA-f3x9-2chm-73c8
  4. 2026-11-16 CVSS score added · GHSA-f3x9-2chm-73c8
  5. 2026-11-16 Weakness changed · GHSA-f3x9-2chm-73c8
  6. 2026-11-16 5 new references · GHSA-f3x9-2chm-73c8

References

  • TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
  • TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
  • TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
  • TI-2026-86049 Unauthenticated SQLite function DoS in Nuxt Content query API CVSS 3.1HIGH 7.5
  • TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
  • TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
See all 52 →

Sources