Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71315 – Authorization Bypass (Route Rule Middleware Bypass) – Nuxt 3.21.7–3.21.9 and 4.4.7–

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71315 is an incorrect-authorization vulnerability (CWE-178 / CWE-863) in Nuxt, the open-source web framework for Vue.js. When case-sensitive routing is disabled, mixed-case routeRules keys fail to match case-folded path lookups, silently dropping appMiddleware authorization gates and allowing unauthenticated access to protected routes. It carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: During route rule matching, Nuxt lowercases the lookup path but does not normalize the configured routeRules keys. Mixed-case keys therefore never match the case-folded lookup, so their associated rules are silently skipped. This is an incomplete fix for CVE-2026-53721.
  • Trigger conditions: Case-sensitive routing is disabled (router.options.sensitive is false, the default) and one or more routeRules use mixed-case keys (for example /Admin/dashboard) to attach an appMiddleware authorization gate.
  • Attack vector: Network — a remote, unauthenticated attacker requests the affected route without triggering the intended middleware.
  • Impact: The appMiddleware auth gate fails to execute, permitting unauthenticated access to protected content, including SSR-fetched data exposure and client-side redirect middleware for protected routes.

Affected software

  • Nuxt 3.x: >= 3.21.7 and < 3.21.10 (i.e., 3.21.7 through 3.21.9)
  • Nuxt 4.x: >= 4.4.7 and < 4.5.1 (i.e., 4.4.7 through 4.5.0)

Severity

  • CVSS v3.1 base score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Nuxt 3.21.10 or Nuxt 4.5.1, which contain the fix.
  • If no patch can be applied:
    • Name all route rules and page files in lowercase exclusively.
    • Enable case-sensitive routing: router: { options: { sensitive: true } }.
    • Implement server-side authentication middleware that does not rely on route rules.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <div id="__nuxt", window.__NUXT__
  • URL of a loaded script: /_nuxt/
  • JavaScript object present once the page runs: $nuxt

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge