Quick answers
- Is CVE-2026-71315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71315 being exploited in the wild.
- How severe is CVE-2026-71315?
- High severity, with a CVSS score of 8.2, published 5 August 2026.
- Which products and versions are affected?
- nuxt (npm) SEMVER:introduced=4.4.7,fixed=4.5.1.
- Is there a fix for CVE-2026-71315?
- Yes. nuxt (npm): upgrade to 4.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71315 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-71315?
- Check whether you run nuxt (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nuxt (npm): upgrade to 4.5.1 or later
npm install nuxt@4.5.1
Technical details
Nuxt matches route rules case-insensitively by default, but an incomplete fix for a previous vulnerability (CVE-2026-53721) resulted in an asymmetric matching process. While the lookup path is folded to lowercase, the route-rule keys compiled into the matcher remain verbatim (mixed-case). Consequently, rules defined with uppercase characters (e.g., /Admin) or derived from PascalCase page files fail to match. This allows attackers to bypass 'appMiddleware' auth gates and other route-level protections by requesting paths that vue-router serves case-insensitively but Nuxt fails to protect. The issue is resolved in versions 4.5.1 and 3.21.10 by ensuring both keys and lookups are normalized symmetrically.
Affected products
- Nuxt nuxt >= 4.4.7, < 4.5.1
- Nuxt nuxt >= 3.21.7, < 3.21.10
Identifiers
- CVE-2026-71315
- GHSA-hxvh-4h3w-prp9
Timeline
- 2026-07-27: disclosed
- 2026-08-05: advisory
- 2026-08-05: patched