CVE-2026-132128: @fastify/middie · Improper Handling of Case Sensitivity
Affects @fastify/middieSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 9.3.7 soon.
Data as of 19 Nov 2026, 11:50 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 7.4 |
|---|
- Patch
- Available – fixed in 9.3.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade @fastify/middie to 9.3.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/middie@fastify/middie | Affected
| Fixed in
|
npm@fastify/middiepkg:npm/@fastify/middieOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @fastify/middie to version 9.3.7 or later where the issue is fixed. As a workaround, enforce authorization in a Fastify hook like preHandler that runs after routing, or keep routing case-sensitive (the default setting).
Description
@fastify/middie versions up to 9.3.6 improperly handle case sensitivity in middleware path matching when the router's caseSensitive setting is false. This allows requests using a percent-encoded KELVIN SIGN character (U+212A) in place of the letter 'k' to bypass middleware protections such as authentication or rate limiting on paths containing 'k'. The issue is fixed in version 9.3.7.