Skip to content
Threat Brief

← All advisories

CVE-2026-132128

High 7.4No known exploitationFix available

@fastify/middie vulnerable to path-scoped middleware bypass via Unicode case folding

Record last updated

CVSS score

7.4

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 42% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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-178, CWE-863

Patching and mitigation

Patch status
Fix available (source: CVE record (openjs))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
@fastify/middie@fastify/middieall versions before 9.3.79.3.7CVE Program
@fastify/middie@fastify/middie (unaffected)9.3.7Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by openjs

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (openjs)

    Source: CVE record (openjs) (opens in a new tab)

Vendor guidance and references