Fastify Middie auth bypass in path-scoped middleware
Affects @fastify/middie 8.3.0 through 9.3.6 when middleware is mounted on an array of paths where an element ends with a slash. Fixed in 9.3.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 9.3.7
- Who is exposed
- Not reported
Summary
@fastify/middie, the middleware engine for Fastify, can let a remote, unauthenticated attacker reach protected routes. Path-scoped middleware such as authentication, authorization, or rate limiting is skipped for some subroutes when it is mounted on an array of paths that includes a path ending in a slash or the root path.
Written by a model
Original description
@fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions 8.3.0 through 9.3.6, the internal helper that normalizes a path-scoped middleware's mount path only handles string inputs, but the use method also accepts an array of mount paths and passes it through unchanged, so the normalization silently does nothing. As a result, a trailing slash on an array element survives into the generated route-matching regular expression, and an element that is exactly the root path, meaning a catch-all mount, is dropped entirely. Requests to subroutes of the affected mount paths then skip the path-scoped middleware, such as authentication, authorization, or rate limiting, while Fastify's router still dispatches them to the handler, allowing an unauthenticated client to reach protected routes. Applications are affected when they mount middleware on an array of paths in which an element ends with a slash, including one introduced by a plugin prefix that ends with a slash, or is exactly the root path. 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 array mount paths with a trailing slash element for security relevant middleware.
Who should check
Teams running @fastify/middie 8.3.0 through 9.3.6 that mount authentication, authorization or rate-limit middleware on an array of paths with a trailing-slash element or the root path /.
“An application is affected when it mounts middleware on an array of paths”
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-132131 (@fastify/middie vulnerable to path-scoped middleware bypass via array mount-path type confusion), 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-132131 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/middie: from 8.3.0, fixed in 9.3.7
Fixed versions: 9.3.7.
Conditions (all must be true for the bug to be hit):
- Middleware is mounted on an array of paths in which an element ends with a slash, including one created by a plugin prefix ending in /, or an element that is exactly / (source: https://github.com/fastify/middie/security/advisories/GHSA-hfwp-44m5-9364)
- Affected @fastify/middie versions are 8.3.0 through 9.3.6 (source: https://github.com/fastify/middie/security/advisories/GHSA-hfwp-44m5-9364)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-132131 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132131 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-hfwp-44m5-9364
- 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-132131
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-132131"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- 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
- Would score about 46 if advisories confirm default setups are exposed
Impact
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/middie · Advisory GHSA-hfwp-44m5-9364 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132131 |
| Record | NVD · CVE-2026-132131 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-132131
Is CVE-2026-132131 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?
Path-scoped middleware such as authentication, authorization, or rate limiting is skipped, while the request still reaches the handler. This means unauthenticated clients can reach protected routes.
Source: github.com
Which versions are affected by CVE-2026-132131?
@fastify/middie (npm): from 8.3.0 before 9.3.7.
Source: cve.now feed data
Am I affected, and how do I check?
The issue is in @fastify/middie versions 8.3.0 through 9.3.6, and only when middleware is mounted on an array of paths where an element ends with a slash, including a plugin prefix ending in /, or an element that is exactly /. To check a installed version, run npm ls @fastify/middie, and review the mount paths passed to middleware in your code.
Source: github.com
How do I fix CVE-2026-132131?
Upgrade @fastify/middie to 9.3.7, which is the fixed version.
Source: github.com
Related
- CVE-2026-112712@fastify/middie vulnerable to path-scoped middleware bypass via scope prefix mismatch
- CVE-2026-85184@fastify/middie vulnerable to path-scoped middleware bypass via absolute-form request target
- CVE-2026-14198@fastify/middie vulnerable to authorization bypass via encoded slash in path parameter values
- CVE-2026-6270@fastify/middie vulnerable to middleware authentication bypass in child plugin scopes
- CVE-2026-22031Fastify Middie Middleware Path Bypass
- CVE-2026-2880@fastify/middie has an improper path normalization vulnerability
No corrections so far. Something wrong on this page? Report an error.