ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-114131

Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass on dynamic and catch-all routes

Published Oct 16, 2026 · catalog updated Oct 29, 2026 · Nuxt: Route rules are

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-114131. EPSS is 0.36%. Act only if a listed version of Nuxt: Route rules are is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Nuxt: Route rules are).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.36%
Remediation
Version ranges on file
Affected products
npm nuxt · package npm

### Summary Nuxt compared keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's never runs, including during server rendering. ### Impact For a page served through a dynamic or catch-all route, an attacker can percent-encode a character in the path to skip the rule: Requesting still renders with decoded to , but the rule keyed does not match, so does not run and the server renders and returns the gated page to an unauthenticated visitor. No privileges and no user interaction are required, and only ASCII characters are involved. Purely static ASCII routes are not affected: static segments are matched without decoding, so a request for does not resolve to the page registered at and 404s instead of rendering. The rule keys affected are the ones carried in the app manifest and consumed by the app: , , , , , and the payload flags derived from , and . If you have pinned or overridden dependency versions below what your Nuxt release declares, a release outside the affected ranges can still be exposed, so do not conclude from a single reproduction that you are unaffected. ### Patches Releases from and are not affected, because their dependency floor requires a version of the underlying HTTP layer that normalises percent-encoding in the request path before routing, which removes the mismatch in a default install. The comparison itself is fixed in and : route-rule keys and lookup paths are now decoded (and, unless is set, case-folded) before they are compared. Reserved escapes such as are left encoded, so decoding cannot introduce extra path segments, and paths that cannot be decoded are matched verbatim. Upgrading to those releases is recommended, since it fixes the comparison rather than relying on a dependency to normalise the input, and it also restores

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm nuxt>= 3.11.0 < 3.21.4
  • npm nuxt>= 3.11.0, < 3.21.4
  • npm nuxt>= 4.0.0 < 4.4.4
  • npm nuxt>= 4.0.0, < 4.4.4
  • package npmversion unspecified

How to fix CVE-2026-114131

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-114131. EPSS is 0.36%. Act only if a listed version of Nuxt: Route rules are is installed.

Which versions are affected?

Compare what you have installed with >= 3.11.0 < 3.21.4, >= 3.11.0, < 3.21.4, >= 4.0.0 < 4.4.4, >= 4.0.0, < 4.4.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-436; CWE-863: Incorrect Authorization. EPSS 0.36%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · GitHub Advisory Database

    Detected

    ### Summary Nuxt compared keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's never runs, including during server rendering. ### Impact For a page served through a dynamic or

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ### Summary Nuxt compared keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's never runs, including during server rendering. ### Impact For a page served through a dynamic or

  3. Oct 29, 2026 · Maintainer security tabs

    Updated

    ### Summary Nuxt compared keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's never runs, including during server rendering. ### Impact For a page served through a dynamic or

Sources

  • CVE.orgVulnerability recordCVE-2026-114131

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114131

    30-day exploitation probability 0.36%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-6gq8-jgmh-3ffp

    Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass on dynamic and catch-all routes

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-114131

    Nuxt compared routeRules keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's appMiddleware never runs, including during server rendering.

    advisories.gitlab.com
  • Maintainer security tabsVendor advisoryGHSA-6gq8-jgmh-3ffp

    ### Summary Nuxt compared keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's never runs, including during server rendering. ### Impact For a page served through a dynamic or

    github.com
  • Snyk Vulnerability DatabasePackage advisorySNYK-JS-NUXT-21431476

    Incorrect Authorization

    security.snyk.io

References

Freshness

Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026
  • FIRST EPSSOct 31, 2026
  • Snyk Vulnerability DatabaseOct 25, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • GitLab Advisory DatabaseOct 23, 2026
  • CVE.orgOct 23, 2026