# CVE-2026-114131: Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-6gq8-jgmh-3ffp

## What is CVE-2026-114131?

CVE-2026-114131 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. From 3.11.0 until 3.21.4 and 4.4.4, Nuxt compares route-rule keys with the raw request path while route resolution decodes dynamic and catch-all parameters, allowing a percent-encoded segment to resolve to a protected page without matching the routeRules entry intended for that path. As a result, appMiddleware can be skipped during server rendering and an unauthenticated requester can receive the gated page and its SSR data. The same mismatch affects app-manifest rules including redirect, appLayout, ssr, prerender, and payload flags derived from cache, isr, and swr. This vulnerability is fixed in 4.4.4 and 3.21.4.

Weakness: CWE-863 (Incorrect Authorization), CWE-436 (Interpretation Conflict)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt` | npm | From 3.11.0 | 3.21.4 |
| `nuxt` | npm | From 3.11.0 | 3.21.4 |
| `nuxt` | npm | From 4.0.0 | 4.4.4 |
| `nuxt` | npm | From 4.0.0 | 4.4.4 |

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

Upgrade nuxt to a fixed version for your release line: 3.21.4 or 4.4.4.

## Is CVE-2026-114131 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- nuxt (npm): affected from 3.11.0; fixed in 3.21.4
- nuxt (npm): affected from 3.11.0; fixed in 3.21.4
- nuxt (npm): affected from 4.0.0; fixed in 4.4.4
- nuxt (npm): affected from 4.0.0; fixed in 4.4.4

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

## Sources

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

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