# CVE-2026-132128: @fastify/middie vulnerable to path-scoped middleware bypass via Unicode case folding


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-r5h5-r25j-5vhr

## What is CVE-2026-132128?

CVE-2026-132128 is a high-severity vulnerability in @fastify/middie, published on 19 Nov 2026. 

### Official description

@fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie does not honor the router's caseSensitive setting and matches path-scoped middleware mount paths with a case-insensitive regular expression that does not fold non-ASCII characters, while Fastify's router, when caseSensitive is set to false, lowercases the request path with a Unicode-aware conversion that maps the KELVIN SIGN character (U+212A) to the ASCII letter k. A request that spells a k in a protected mount path as the percent-encoded KELVIN SIGN is therefore routed to the protected handler while the middleware mounted on that path, such as authentication, authorization, or rate limiting, never matches and is skipped, letting an unauthenticated client reach the handler. Only applications that set caseSensitive to false and protect a mount path containing the letter k are affected. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, or keep routing case-sensitive, which is the default.

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

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

1 open source package ship an affected version, including %40fastify/middie.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `%40fastify/middie` | npm | `pkg:npm/%40fastify/middie` | All versions | 9.3.7 |

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

Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.

## Is CVE-2026-132128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132128 is a high-severity vulnerability in @fastify/middie, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132128 in the wild and no public exploit code.

Affected packages and fixed versions:
- %40fastify/middie (npm): affected all versions; fixed in 9.3.7

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

## Sources

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

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