Servers and applications
CVE-2026-53721
Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
- Severity
- High
- Published
- 2 Jun 2026
- Last changed
- 10 Jun 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.21.7, 4.4.7
- Exploit chance
- 0.4% in the next 30 daysHigher than 34% of CVEs. EPSS by FIRST, 19 Nov 2026
- Also known as
- GHSA-mm7m-92g8-7m47
- Sources
- Project advisories (GitHub)
Description
Nuxt looks up routeRules for the current navigation by calling getRouteRules({ path: to.path }) from the page-router plugin and the no-pages router plugin. The compiled routeRules matcher (built on rou3) performs case-sensitive matching, while vue-router is configured with its default sensitive: false and matches paths case-insensitively.
The two routers therefore disagree on which rules apply to a given request path: vue-router still matches the page record for /Admin/dashboard, but the routeRules lookup for the same path returns no match. Any appMiddleware declared via routeRules is never added to the middleware set and never runs, on both SSR and client navigations. The same path skips other path-keyed route rules in the same way (ssr, redirect, appLayout, and the prerender / payload hints used client-side).
For applications using routeRules with appMiddleware as an authorization gate (a documented pattern), an attacker can flip the case of any static segment in a protected URL…
Workarounds
Until you can upgrade, you can mitigate by either:
- Setting router.options.sensitive = true so vue-router matches case-sensitively (this changes route-matching behaviour app-wide).
- Moving security-critical middleware off routeRules.appMiddleware and onto definePageMeta({ middleware: [...] }) on the protected page components, which is bound to the matched record.
- Enforcing authorization at the API / data-fetching layer (which you should be doing in any case).
Affected software
| Software | Affected versions |
|---|---|
NuxtServers and applications · github:nuxt/nuxt |
|
About Nuxt
JavaScript framework
- Developers who used it in the past year
- 4%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 3,404,733npm, 15 Nov 2026
- GitHub stars
- 61,078GitHub, 15 Nov 2026
- Forks
- 5,837GitHub, 15 Nov 2026
- Latest release
- v4.6.4GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- JavaScript, Vue.jsWikidata
- First published on GitHub
- 26 Oct 2016GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4 | 4.6.4 | Yes |
| 3 | 3.21.11 | Ended 31 Jul 2026 |
| 2 | 2.18.1 | Ended 30 Jun 2024 |
| 1 | 1.4.5 | Ended 21 Sept 2019 |
From endoflife.date.
Vulnerabilities in Nuxt
- In our list
- 49
- Published in the last 12 months
- 46
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- CVE-2023-54417Nuxt 3.0.0 < 3.4.2 Unauthenticated File Read via vite-node Dev ServerHigh 8.7 18 Nov 2026
- CVE-2023-54418Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev ServerHigh 8.7 18 Nov 2026
- GHSA-r99w-jh2x-3mg9Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- CVE-2026-128077Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- GHSA-hf59-9xwc-2g4pColliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
- CVE-2026-128076Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53721
- GitHub Advisory Database https://github.com/advisories/GHSA-mm7m-92g8-7m47
- github.com https://github.com/nuxt/nuxt/security/advisories/GHSA-mm7m-92g8-7m47