Fastify Express path-scoped middleware bypass via URL decoding mismatch
Affects @fastify/express before 4.0.10 when path-scoped Express middleware is mounted on a route, such as auth middleware on a parameterized prefix. Fixed in 4.0.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.10
- Who is exposed
- Default setups
Summary
@fastify/express, a compatibility layer that runs Express middleware inside Fastify, can be tricked into skipping path-scoped middleware such as authentication, authorization, or rate limiting while still running the protected route handler. An attacker can exploit this remotely without logging in by sending specially crafted request URLs.
Written by a model
Original description
@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions before 4.0.10, the plugin passes Express a request URL that does not always match the path Fastify's router dispatched, so path-scoped Express middleware can be skipped while the route handler still runs. Several request forms trigger the mismatch, including percent-decoding that rewrites a backslash to a slash or double-decodes an encoded percent sign, and a request target that begins with an asterisk, so the middleware and the handler disagree on the path or on parameter and query values. An unauthenticated client can therefore reach a handler that an authentication, authorization, or rate-limiting middleware was meant to protect, with no special configuration required. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 4.0.10.
Workaround: Enforce authentication in a Fastify preHandler hook based on request.routeOptions.url, or reject request targets starting with * or containing a backslash in an onRequest hook registered before @fastify/express.
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-133120 (@fastify/express vulnerable to path-scoped middleware bypass via request URL decoding and normalization mismatches), 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-133120 (entry last updated 2026-11-21):
Affected:
- npm package @fastify/express: fixed in 4.0.10
Fixed versions: 4.0.10.
Conditions (all must be true for the bug to be hit):
- Path-scoped Express middleware mounted on a route, such as an auth middleware on a parameterized prefix (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-w877-hjcp-88rc)
- Percent-decoding forms apply from 4.0.3 onward; request targets starting with * apply in every release (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-w877-hjcp-88rc)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Enforce authentication in a Fastify preHandler hook based on request.routeOptions.url, or reject request targets starting with * or containing a backslash in an onRequest hook registered before @fastify/express. (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-w877-hjcp-88rc)
CISA KEV: CVE-2026-133120 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133120 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/fastify-express/security/advisories/GHSA-w877-hjcp-88rc
- 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-133120
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-133120"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach10/20Affects npm packages
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
Impact
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/fastify-express · Advisory GHSA-w877-hjcp-88rc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133120 |
| Record | NVD · CVE-2026-133120 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-133120
Is CVE-2026-133120 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?
The plugin percent-decodes the URL before Express parses it, and request targets starting with * are handled differently. Path-scoped Express middleware, such as authentication mounted on a parameterized prefix, can therefore be skipped for matching requests.
Source: github.com
Which versions are affected by CVE-2026-133120?
@fastify/express (npm): before 4.0.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions before 4.0.10 are affected. Percent-decoding forms apply from 4.0.3 onward, and request targets starting with * apply in every release. To check, run npm ls @fastify/express to see the installed version, and look for path-scoped Express middleware mounted with route parameters.
Source: github.com
How do I fix CVE-2026-133120?
Upgrade @fastify/express to 4.0.10. The facts name no vendor patch ids. If you cannot upgrade yet, see the workaround for the interim.
Source: github.com
Related
- CVE-2026-129504@fastify/express vulnerable to path-scoped middleware bypass via prefix and mount path join mismatch
- CVE-2026-124626@fastify/express vulnerable to middleware bypass via empty route parameters and wildcards
- CVE-2026-133867@fastify/express vulnerable to middleware bypass via RegExp mount paths under parameterized prefixes
- CVE-2026-112362@fastify/express vulnerable to path-scoped middleware bypass via absolute-form request targets
- CVE-2026-6556@fastify/express vulnerable to middleware bypass via non-string mount paths in prefixed plugins
- CVE-2026-33807@fastify/express vulnerable to middleware path doubling causing authentication bypass in child plugin scopes
No corrections so far. Something wrong on this page? Report an error.