Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114131 Overview
CVE-2026-114131 is a route-rule bypass vulnerability in Nuxt, the open-source web development framework for Vue.js. Nuxt compares routeRules keys against the raw request path, while route resolution decodes dynamic and catch-all parameters. A percent-encoded URL segment can therefore resolve to a protected page without matching the routeRules entry intended for that path. The flaw affects versions 3.11.0 through 3.21.3 and 4.4.3, and is fixed in 3.21.4 and 4.4.4. The issue is classified as an interpretation conflict [CWE-436].
Critical Impact
Unauthenticated requesters can bypass appMiddleware during server-side rendering and receive gated pages along with their SSR data. The same mismatch skips app-manifest rules including redirect, appLayout, ssr, prerender, and payload flags derived from cache, isr, and swr.
Affected Products
- Nuxt 3.11.0 through 3.21.3
- Nuxt 4.0.0 through 4.4.3
- Applications relying on routeRules or appMiddleware for access control
Discovery Timeline
- 2026-10-21 - CVE-2026-114131 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114131
Vulnerability Analysis
Nuxt resolves route rules by comparing the raw HTTP request path against configured routeRules keys. The router that resolves pages, however, decodes percent-encoded dynamic and catch-all parameters before matching. This asymmetry means that a request such as /%61dmin resolves to the /admin page component, but fails to match the routeRules['/admin'] entry that would normally attach appMiddleware, authentication guards, or server-rendering flags.
During server-side rendering, the gated page is rendered and its serialized SSR payload is returned to the unauthenticated requester. Beyond middleware skipping, the mismatch also affects app-manifest derived rules. Rules controlling redirect, appLayout, ssr, prerender, and payload flags from cache, isr, and swr can all be bypassed through the same path-encoding trick.
Root Cause
The root cause is a decoding inconsistency between two subsystems that both consume the request path. The route-rule matcher used raw path strings, while the page router applied decodeURI on dynamic segments. The patch introduces a decodeRoutePath helper and a normalizeRouteRulePath function so both subsystems match on decoded, optionally case-folded forms.
Attack Vector
An unauthenticated remote attacker crafts a URL in which one or more characters of a protected path are percent-encoded. The server resolves the request to the protected page, skips the associated middleware, and returns the rendered HTML and SSR data. No authentication, user interaction, or special privileges are required.
// Security patch - packages/nuxt/src/core/utils/index.ts
// fix(nuxt): match route rules against decoded paths
/**
* Decode a route path for route-rule matching, returning it unchanged if it is not
* percent-encoded or cannot be decoded. Reserved characters (`%2F`, `%3F`, …) are
* left encoded, so decoding cannot introduce additional path segments. Only the path
* portion is decoded; a query string, if present, is left untouched to avoid
* double-decoding it.
*/
export function decodeRoutePath (path: string) {
if (!path.includes('%')) { return path }
const queryIndex = path.indexOf('?')
const pathname = queryIndex === -1 ? path : path.slice(0, queryIndex)
try {
return queryIndex === -1 ? decodeURI(pathname) : decodeURI(pathname) + path.slice(queryIndex)
} catch {
return path
}
}
Source: Nuxt commit 81f86ac5
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114131
Indicators of Compromise
- HTTP access logs showing successful 200 responses to percent-encoded variants of protected routes (for example /%61dmin, /%41dmin) from unauthenticated clients.
- Server-rendered responses containing SSR payload data for pages that should require authentication.
- Absence of expected middleware log entries for requests that resolved to gated pages.
Detection Strategies
- Replay requests with mixed percent-encoded characters against known protected routes and compare responses to the canonical path.
- Correlate request paths at the reverse proxy with route-rule enforcement decisions emitted by Nuxt middleware to identify mismatches.
- Inspect application dependency manifests for Nuxt versions between 3.11.0 and 3.21.3, or 4.0.0 and 4.4.3.
Monitoring Recommendations
- Alert on HTTP requests to internal or administrative paths that contain % characters in path segments.
- Monitor outbound SSR payload sizes on sensitive routes to detect unauthorized rendering.
- Track changes in authentication middleware invocation counts relative to request volume.
How to Mitigate CVE-2026-114131
Immediate Actions Required
- Upgrade Nuxt to 3.21.4 or 4.4.4 as soon as possible, which includes the decodeRoutePath normalization fix.
- Audit all routeRules and appMiddleware definitions and confirm which routes depend on them for authorization.
- Review SSR payloads for sensitive data that would be exposed if middleware is bypassed.
Patch Information
The fix is delivered in Nuxt v3.21.11 and Nuxt v4.5.2, with the corrective changes in commits 81f86ac5 and 9123ed85. Full details are available in the GitHub Security Advisory GHSA-6gq8-jgmh-3ffp.
Workarounds
- Normalize request paths at the reverse proxy or edge (for example Nginx, Cloudflare Workers) by decoding percent-encoded characters before they reach the Nuxt server.
- Enforce authorization inside page components or server routes rather than relying solely on routeRules and appMiddleware.
- Reject requests containing percent-encoded alphanumeric characters in path segments where no legitimate use case exists.
# Upgrade Nuxt to a patched release
npm install nuxt@4.5.2
# or for the 3.x branch
npm install nuxt@3.21.11
# Verify installed version
npx nuxi info | grep -i nuxt
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

