Description
Nuxt is an open-source web development framework for Vue.js. From versions 3.11.0 to before 3.21.7 and 4.0.0 to before 4.4.7, there is a route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher. This issue has been patched in versions 3.21.7 and 4.4.7.
Published: 2026-06-12
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Nuxt is an open‑source framework for Vue.js. Between versions 3.11.0 and before 3.21.7, and between 4.0.0 and before 4.4.7, the framework allows a route‑rule middleware bypass due to a case‑sensitivity mismatch between vue‑router and the internal routeRules matcher. An attacker who can supply a URL path with altered case can cause the middleware logic to fail, effectively granting the attacker access to content or functionality that should be guarded. This flaw is rooted in improper handling of input case sensitivity (CWE‑178) and missing or weak authorization checks (CWE‑863), and it can lead to unauthorized reading of protected resources. Based on the description, it is inferred that the attacker crafts a URL with altered case to exercise the bypass.

Affected Systems

Nuxt framework versions 3.11.0 through 3.21.6 inclusive and 4.0.0 through 4.4.6 inclusive are affected. The vulnerability was patched in versions 3.21.7 and 4.4.7.

Risk and Exploitability

The CVSS score of 8.8 categorizes this as a high‑severity vulnerability. The EPSS score of less than 1% indicates a low likelihood of widespread exploitation at this time. The vulnerability is not listed in the CISA KEV catalog. An attacker could exploit the issue by crafting a URL with a different case than the defined route, causing the application to bypass middleware checks. The attack requires the ability to access the target application’s URLs, and the potential impact includes unauthorized access to protected content or functionality. Based on the description, it is inferred that the attacker would need to target the application’s public‑facing routes to achieve the bypass.

Generated by OpenCVE AI on June 12, 2026 at 15:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Nuxt to version 3.21.7 or later, or 4.4.7 or later, to apply the vendor’s fix for the case‑sensitivity mismatch.
  • Verify that all routes intended to be protected by middleware are still guarded after the upgrade, ensuring no unintended exposure of sensitive pages.
  • Implement or enforce strict case sensitivity checks on route paths in the application logic to prevent future mismatches that could lead to similar bypasses.

Generated by OpenCVE AI on June 12, 2026 at 15:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 12 Jun 2026 15:45:00 +0000

Type Values Removed Values Added
First Time appeared Nuxt
Nuxt nuxt
Vendors & Products Nuxt
Nuxt nuxt

Fri, 12 Jun 2026 14:30:00 +0000

Type Values Removed Values Added
Description Nuxt is an open-source web development framework for Vue.js. From versions 3.11.0 to before 3.21.7 and 4.0.0 to before 4.4.7, there is a route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher. This issue has been patched in versions 3.21.7 and 4.4.7.
Title Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
Weaknesses CWE-178
CWE-863
References
Metrics cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-06-12T13:41:34.022Z

Reserved: 2026-06-10T16:43:31.241Z

Link: CVE-2026-53721

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-06-12T15:16:31.297

Modified: 2026-06-12T16:01:25.477

Link: CVE-2026-53721

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-12T16:00:21Z

Weaknesses
  • CWE-178

    Improper Handling of Case Sensitivity

  • CWE-863

    Incorrect Authorization