CVE-2026-53721: Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
Impact 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.
Published Jun 16, 2026
Affected packages
nuxt
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 4.4.7
- Fixed in
- 4.4.7
- Check
npm ls nuxt
nuxt
- Ecosystem
- npm
- Affected
- >= 3.11.0, < 3.21.7
- Fixed in
- 3.21.7
- Check
npm ls nuxt
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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 (for example /Admin/dashboard instead of /admin/dashboard) to render the protected page with the middleware skipped. The server returns the fully server-rendered page including any useFetch / useAsyncData results captured during SSR.
This is an instance of CWE-178 (Improper Handling of Case Sensitivity) leading to CWE-863 (Incorrect Authorization) for apps that treat appMiddleware as an authorization boundary.
Mitigating factors
- Only affects apps that use
routeRules.appMiddleware. The more idiomaticdefinePageMeta({ middleware })is bound to the matched route record and is unaffected. - Nuxt route middleware is documented as an app-layer concern, not a server-side auth boundary; well-built apps enforce authorization again at the API / data-fetching layer.
- Apps that explicitly set
router.options.sensitive = trueare not affected.
Patches
Fixed in [email protected] (commit `07e39cd6`) and backported to [email protected] (commit `3f3e3fa7`). The fix normalizes the path used for routeRules lookups so it matches vue-router's default case-insensitive semantics.
Workarounds
Until you can upgrade, you can mitigate by either:
- Setting
router.options.sensitive = trueso vue-router matches case-sensitively (this changes route-matching behaviour app-wide). - Moving security-critical middleware off
routeRules.appMiddlewareand ontodefinePageMeta({ 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).
Credit
Reported by Anthropic / Claude through Anthropic's coordinated vulnerability disclosure process. Reference: ANT-2026-9FSEBYMC.
References
- https://github.com/nuxt/nuxt/security/advisories/GHSA-mm7m-92g8-7m47
- https://nvd.nist.gov/vuln/detail/CVE-2026-53721
- https://github.com/nuxt/nuxt/commit/07e39cd6f26e407b4192b7865bd17bc44536b9bb
- https://github.com/nuxt/nuxt/commit/3f3e3fa7b5eec8e495f4f8ce0a54813a8875a11e
- https://github.com/advisories/GHSA-mm7m-92g8-7m47
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-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
medium6.5No fixNov 16, 2026CVE-2026-128074
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
medium6.9Nov 16, 2026CVE-2026-128075
Nuxt exposes the message and data of unhandled errors thrown during server rendering
medium5.3No fixNov 16, 2026CVE-2026-128076
Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
low3.1No fixNov 16, 2026CVE-2026-119200
Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
medium6.5Oct 30, 2026CVE-2026-114130
Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled
low2.3Oct 22, 2026
