Skip to main content
Menu
CVEs

Fastify Middie middleware bypass via doubled slashes in mount paths

CVE-2026-132133EUVD-2026-129772Published November 19, 2026, updated

4.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 9.3.7
Who is exposed
Not reported

Summary

The @fastify/middie middleware engine can be bypassed remotely, without logging in, when the ignoreDuplicateSlashes option is enabled and a middleware mount path contains a doubled slash. Path-scoped middleware such as authentication, authorization, or rate limiting is skipped, so an attacker can reach the protected handler behind it.

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 builds the match regular expression for each path-scoped middleware from its mount path without collapsing duplicate slashes, even when the application enables the ignoreDuplicateSlashes router option. Under that option Fastify's router collapses duplicate slashes in both the registered route and the request path, so a mount path containing a doubled slash is served by the router at its single-slash form while the middleware's compiled match still requires the doubled slash and never matches. A path-scoped middleware such as authentication, authorization, or rate limiting is therefore skipped while the router dispatches the request to the protected handler, without any authentication required. Applications are affected when they enable ignoreDuplicateSlashes and a middleware mount path reaches middie with a duplicate slash, most commonly when a plugin prefix that ends with a slash is joined to a mount path that starts with one. 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, and avoid mount paths and plugin prefixes that introduce duplicate slashes.

What to do

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-132133 (@fastify/middie vulnerable to path-scoped middleware bypass via duplicate-slash mount path), 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-132133 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/middie: fixed in 9.3.7
Fixed versions: 9.3.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132133 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132133 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-56jq-34pf-p873
- 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-132133
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-132133"}.

Affected versions

cve.now Index

38Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach16/20@fastify/middie: 2.8M downloads a week
  • Severity4.8/10CVSS 4.8
  • No patch0/5No signal

What would change the score

  • Would score about 83 if added to CISA KEV
  • Would score about 78 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

Impact

Timeline

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

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

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fastify/middie · Advisory GHSA-56jq-34pf-p873
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132133
RecordNVD · CVE-2026-132133
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-132133

Is CVE-2026-132133 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

Which versions are affected by CVE-2026-132133?

@fastify/middie (npm): before 9.3.7.

Source: cve.now feed data

How do I fix CVE-2026-132133?

Upgrade to a fixed version: 9.3.7.

Source: cve.now feed data

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