# CVE-2026-114132: Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** CLSA-2026-1793181427, CLSA-2026-1793181586, CLSA-2026-1793181946, CLSA-2026-1793182024, GHSA-vjh5-4x84-xrqp

## What is CVE-2026-114132?

CVE-2026-114132 is a medium-severity vulnerability in nuxt, published on 21 Oct 2026. 

### Official description

Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.2, Nuxt resolves pages case-insensitively by default while Nitro matches server-side route-rule keys case-sensitively, allowing a request whose path differs only by letter case to render without the server rule intended for that page. The mismatch can skip redirect, headers, proxy, ssr: false, and noScripts, and can cause getRouteRules(event) and matchRouteRules to return no rule for the case variant. Applications that set router.options.sensitive: true in nuxt.config are not affected; setting sensitive only in app/router.options.ts does not establish this exclusion because the server follows the nuxt.config value. Access checks implemented in server middleware, page route middleware, or page data fetching remain independent of this matcher. This issue is fixed in version 4.6.2.

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

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

8 open source packages ship an affected version, including @nuxt/nitro-server and nuxt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nuxt/nitro-server` | npm | From 3.20.0 | None |
| `@nuxt/nitro-server` | npm | From 3.20.0 | None |
| `@nuxt/nitro-server` | npm | From 4.2.0 | 4.6.2 |
| `@nuxt/nitro-server` | npm | From 4.2.0 | 4.6.2 |
| `nuxt` | npm | From 3.0.0 | None |
| `nuxt` | npm | From 3.0.0 | None |
| `nuxt` | npm | From 4.0.0 | 4.6.2 |
| `nuxt` | npm | From 4.0.0 | 4.6.2 |

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

Upgrade @nuxt/nitro-server to 4.6.2 or later.

## Is CVE-2026-114132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114132 is a medium-severity vulnerability in nuxt, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114132 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/nitro-server (npm): affected from 3.20.0; no fix listed
- @nuxt/nitro-server (npm): affected from 3.20.0; no fix listed
- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.6.2
- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.6.2
- nuxt (npm): affected from 3.0.0; no fix listed
- nuxt (npm): affected from 3.0.0; no fix listed
- nuxt (npm): affected from 4.0.0; fixed in 4.6.2
- nuxt (npm): affected from 4.0.0; fixed in 4.6.2

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-114132/ (Markdown: https://insights.sbomify.com/CVE-2026-114132/index.md)
```

## Sources

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

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