# CVE-2026-71315: Nuxt route rules silently dropped for mixed-case paths, bypassing appMiddleware auth gates (incomplete fix for CVE-2026-53721)

> Attackers can bypass authentication middleware by using mixed-case paths when case sensitivity is disabled, allowing unauthorized access to protected routes.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-hxvh-4h3w-prp9

## What is CVE-2026-71315?

CVE-2026-71315 is a high-severity authentication bypass vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nuxt is an open-source web development framework for Vue.js. From 3.21.7 until 3.21.10 and 4.5.1, mixed-case routeRules keys can fail to match case-folded lookups when router.options.sensitive is false and drop appMiddleware authorization gates. This is caused by an incomplete fix for CVE-2026-53721. This issue is fixed in 3.21.10 and 4.5.1.

Weakness: CWE-863 (Incorrect Authorization), CWE-178 (Improper Handling of Case Sensitivity)

## Which versions are affected by CVE-2026-71315?

4 open source packages ship an affected version, including nuxt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.21.7 | 3.21.10 |
| `nuxt` | npm | From 3.21.7 | 3.21.10 |
| `nuxt` | npm | From 4.4.7 | 4.5.1 |
| `nuxt` | npm | From 4.4.7 | 4.5.1 |

## How do I fix CVE-2026-71315?

Upgrade nuxt to a fixed version for your release line: 3.21.10 or 4.5.1.

## Is CVE-2026-71315 being exploited?

There is no known exploitation of CVE-2026-71315 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71315 and fix it if it is affected.

What it is: CVE-2026-71315 is a high-severity authentication bypass vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71315 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt (npm): affected from 3.21.7; fixed in 3.21.10
- nuxt (npm): affected from 3.21.7; fixed in 3.21.10
- nuxt (npm): affected from 4.4.7; fixed in 4.5.1
- nuxt (npm): affected from 4.4.7; fixed in 4.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71315/ (Markdown: https://insights.sbomify.com/CVE-2026-71315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71315
- OSV: https://osv.dev/vulnerability/CVE-2026-71315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71315/
Summaries are generated and may contain mistakes; the official description above is the record.