CVE-2026-71315
Nuxt routeRules case mismatch can bypass appMiddleware auth in certain versions.
Is CVE-2026-71315 being exploited?
Not confirmed. CVE-2026-71315 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-71315?
CVE-2026-71315 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71315?
Yes. A fix has been recorded for CVE-2026-71315. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71315 affect?
CVE-2026-71315 affects Nuxt 3.21.7 - 3.21.9, Nuxt 4.5.0, Nuxt apps using mixed-case routeRules with router.options.sensitive=false. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71315?
Upgrade to Nuxt 3.21.10 or 4.5.1 and audit routeRules/middleware case handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Mixed-case routeRules can skip appMiddleware authorization, allowing attackers to access protected routes and potentially perform unauthorized actions or RCE.
Patch when possible
- affected>= 4.4.7 and < 4.5.1
- affected>= 3.21.7 and < 3.21.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.