CVE-2026-132128
HIGHDescription
@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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-178 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-27636 | Medium | 5.6 | 97% | - | Fix |
| CVE-2021-24347 | High | 8.8 | 54% | - | Fix |
| CVE-2020-12812 | Critical | 9.8 | 45% | KEV + Ransom | Fix |
| CVE-2003-0411 | High | 7.5 | 25% | - | - |
| CVE-2026-47323 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-9845 | Critical | 9.8 | 13% | - | Fix |
Common questions
How do I fix CVE-2026-132128?
No published fix for CVE-2026-132128 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-132128?
CVE-2026-132128 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-132128
Markdown
[](https://tridentstack.com/cve/CVE-2026-132128)HTML
<a href="https://tridentstack.com/cve/CVE-2026-132128"><img src="https://tridentstack.com/cve/badge/CVE-2026-132128.svg" alt="CVE-2026-132128"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-19.