Interpretation Conflict Affecting nuxt package, versions >=3.0.0 <4.6.4


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.27% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JS-NUXT-22552417
  • published15 Nov 2026
  • disclosed13 Nov 2026
  • creditRiahi Foudhil

Introduced: 13 Nov 2026

NewCVE-2026-128071  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

Upgrade nuxt to version 4.6.4 or higher.

Overview

Affected versions of this package are vulnerable to Interpretation Conflict via routeRules matching in the route-rules resolution logic, which compares route rules against the raw request path while leaving encoded slashes (%2F) encoded. A catch-all page route such as app/pages/[...slug].vue or a custom multi-segment page route decodes %2F into a route parameter, creating a mismatch where getRouteRules returns an incomplete result. An unauthenticated attacker can send a request with %2F in the path to render a page without the redirect, headers, proxy, ssr, noScripts, appMiddleware, or appLayout rules configured for the decoded path.

Note: Protected content is exposed only when the page interprets the decoded parameter accordingly: a custom multi-segment parameter resolves the decoded path directly, while a repeatable catch-all exposes it only when the page joins the slug array with /; pages that load content via route.path are not affected because that property retains the encoding.

Workaround

Add a server middleware that rejects requests whose path contains an encoded slash:

// server/middleware/encoded-slash.ts
export default defineEventHandler((event) => {
  if (/%2f/i.test(event.path.split('?')[0])) {
    throw createError({ statusCode: 404 })
  }
})

Narrow the check to the path prefixes your route rules protect if you need to allow encoded slashes elsewhere (e.g. scoped package names). A reverse proxy or CDN that rejects or decodes encoded slashes before forwarding the request also removes the mismatch.

CVSS Base Scores

version 4.0
version 3.1