Skip to main content
Menu
CVEs

Fastify Middie path-scoped middleware bypass via Unicode case folding

Affects @fastify/middie 9.3.6 and earlier when Fastify runs with caseSensitive: false and the protected mount path contains the letter k. No vendor rating is given beyond the CVSS score of 7.4.

CVE-2026-132128Published November 19, 2026, updated

7.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 9.3.7
Who is exposed
Specific setups only

Summary

@fastify/middie, the middleware engine for Fastify, lets a remote, unauthenticated attacker skip path-scoped middleware such as authentication, authorization, or rate limiting and reach the protected handler. It only affects applications that turn off case-sensitive routing and protect a path containing the letter k, where a specially encoded Unicode request bypasses the middleware.

Written by a model

Original 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.

Who should check

Teams running @fastify/middie 9.3.6 or earlier on Fastify with caseSensitive: false and path-scoped middleware on mount paths containing the letter k, such as auth or rate limiting.

“@fastify/middie versions <= 9.3.6 do not read routerOptions.caseSensitive”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Fastify routing is set to case-insensitive (caseSensitive: false) @fastify/middie version 9.3.6 or earlier The protected mount path contains the letter k
  2. Upgrade to a fixed version: 9.3.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132128 (@fastify/middie vulnerable to path-scoped middleware bypass via Unicode case folding), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132128 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/middie: fixed in 9.3.7
Fixed versions: 9.3.7.
Conditions (all must be true for the bug to be hit):
- Fastify routing is set to case-insensitive (caseSensitive: false) (source: https://github.com/fastify/middie/security/advisories/GHSA-r5h5-r25j-5vhr)
- @fastify/middie version 9.3.6 or earlier (source: https://github.com/fastify/middie/security/advisories/GHSA-r5h5-r25j-5vhr)
- The protected mount path contains the letter k (source: https://github.com/fastify/middie/security/advisories/GHSA-r5h5-r25j-5vhr)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-132128 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132128 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/middie/security/advisories/GHSA-r5h5-r25j-5vhr
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132128
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132128"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach16/20@fastify/middie: 2.8M downloads a week
  • Severity8.4/10CVSS 7.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fastify/middie · Advisory GHSA-r5h5-r25j-5vhr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132128
RecordNVD · CVE-2026-132128
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-132128

Is CVE-2026-132128 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A client can spell a k in the mount path as the Unicode Kelvin sign (%E2%84%AA) and reach the protected handler without passing the authentication, authorization or rate limiting middleware mounted on that path.

Source: github.com

Which versions are affected by CVE-2026-132128?

@fastify/middie (npm): before 9.3.7.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of @fastify/middie 9.3.6 and earlier are affected, and only when the application enables caseSensitive: false and the protected mount path contains the letter k. To check, look at the installed @fastify/middie version (for example with npm ls @fastify/middie) and at the caseSensitive setting in the Fastify configuration.

Source: github.com

How do I fix CVE-2026-132128?

Upgrade @fastify/middie to 9.3.7 or later, which is the fixed version listed in the affected range.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.