CVE-2026-114132

Nuxt: Server-side route rules (redirect, headers, proxy, ssr) are skipped for case-variant paths when routing is case-insensitive

With the default router.options.sensitive: false, Nuxt's page router resolves routes case-insensitively, so /Admin renders the same page as /admin. On the server, however, route rules were resolved with Nitro's route-rule matcher, which matches keys case-sensitively. A request whose path differs from a rule key only in letter case therefore rendered the page with none of that rule applied.

Earlier fixes (GHSA-mm7m-92g8-7m47, GHSA-hxvh-4h3w-prp9) case-folded the route rules that the Nuxt app itself reads, such as appMiddleware. This advisory covers the rules applied on the server:

• redirect: a rule used to send visitors away from a page, such as '/admin/**': { redirect: '/login' }, was skipped, and the page and its server-fetched data were rendered instead.
• headers: per-route response headers, including security headers such as Content-Security-Policy or X-Frame-Options, were not sent.
• proxy: the request was not proxied.
• ssr: false and noScripts: the page was server-rendered, or shipped scripts, despite the rule.
• getRouteRules(event) (auto-imported, or from nuxt/server) and matchRouteRules from nuxt/server returned no rules for the case variant.

export default defineNuxtConfig({
  routeRules: {
    '/admin/**': { redirect: '/login' },
  },
})

With this configuration, /admin/secret redirects to /login, but /Admin/secret rendered app/pages/admin/secret.vue.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

Already deployed Kodem?

Fixed in [email protected]. Nuxt 3 reached end of life on 31 July 2026 and will not receive a fix.

Nuxt now resolves server-side route rules itself, decoding and case-folding both the rule keys and the request path unless router.options.sensitive is set, and applies the result to Nitro's redirect, headers and proxy handling, the renderer, and the getRouteRules / matchRouteRules helpers.

When routing is case-insensitive, patched releases change some behaviour:

• Route rules also apply to case variants of server API routes. For example, /API/x now matches a /api/** proxy or headers rule.
• Rule keys that differ only in letter case now resolve to the same path on the server, and the later key takes precedence.

The following are not changed by this fix:

• cache and swr response caching is attached to server routes by Nitro's router, which matches case-sensitively. A case variant is still rendered with its route rules applied, but its response is not cached.
• Rules that a deployment preset compiles into platform configuration (for example Vercel's config.json or Netlify's _redirects and _headers) are matched by the platform. Once a request reaches the Nuxt server, the rules are applied as described above.
• If sensitive is set only in app/router.options.ts, the server follows the nuxt.config value. In that configuration route rules can only apply to more paths, never fewer.

1. What is CVE-2026-114132? CVE-2026-114132 is a medium-severity incorrect authorization vulnerability in nuxt (npm), affecting versions >= 4.0.0, < 4.6.2. It is fixed in 4.6.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which packages are affected by CVE-2026-114132?
   • nuxt (npm) (versions >= 4.0.0, < 4.6.2)
   • @nuxt/nitro-server (npm) (versions >= 4.2.0, < 4.6.2)
3. Is there a fix for CVE-2026-114132? Yes. CVE-2026-114132 is fixed in 4.6.2. Upgrade to this version or later.
4. Is CVE-2026-114132 exploitable, and should I be worried? Whether CVE-2026-114132 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-114132 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-114132?
   • Upgrade nuxt to 4.6.2 or later
   • Upgrade @nuxt/nitro-server to 4.6.2 or later

Other vulnerabilities in nuxt