Fastify Express auth bypass in middleware via empty route parameters
Affects @fastify/express 4.0.5 up to 4.0.10 where a Fastify route and an Express middleware mount share a dynamic path pattern. Fixed in 4.0.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.10
- Who is exposed
- Not reported
Summary
@fastify/express, a compatibility layer that runs Express middleware inside Fastify, can be reached remotely without logging in. A request with an empty route parameter or wildcard value can skip path-scoped middleware and reach a protected handler.
Written by a model
Original description
@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions 4.0.5 through 4.0.9, the plugin matches path-scoped Express middleware with a matcher that requires a non-empty value for a dynamic segment, while Fastify's router accepts an empty parameter or wildcard value. When a route and an Express middleware mount share a dynamic pattern, a request with an empty segment matches the Fastify route and runs the handler while the middleware mounted on that pattern is skipped, so on a scoped mount an unauthenticated request can reach a protected handler. No special configuration is required, and the practical impact depends on what the empty value selects in the application. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.
Who should check
Teams running @fastify/express 4.0.5 through 4.0.9 with Express middleware mounted on dynamic paths such as /tenant/:tenantId, including apps that share a route pattern with that middleware.
“>= 4.0.5, < 4.0.10”
What to do
Upgrade to a fixed version: 4.0.10.
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-124626 (@fastify/express vulnerable to middleware bypass via empty route parameters and wildcards), 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-124626 (entry last updated 2026-11-21):
Affected:
- npm package @fastify/express: from 4.0.5, fixed in 4.0.10
Fixed versions: 4.0.10.
Conditions (all must be true for the bug to be hit):
- @fastify/express versions 4.0.5 up to 4.0.10 (affected range >= 4.0.5, < 4.0.10) (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-662w-h4p6-jq4p)
- A Fastify route and an Express middleware mount share a dynamic path pattern (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-662w-h4p6-jq4p)
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-124626 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124626 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-662w-h4p6-jq4p
- 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-124626
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-124626"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- 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
- Would score about 41 if advisories confirm default setups are exposed
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-662w-h4p6-jq4p |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-124626 |
| Record | NVD · CVE-2026-124626 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-124626
Is CVE-2026-124626 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?
An unauthenticated request with an empty path segment can reach a protected Fastify handler while scoped Express middleware, such as authentication, is skipped. The practical impact depends on what the empty value selects in the application.
Source: github.com
Which versions are affected by CVE-2026-124626?
@fastify/express (npm): from 4.0.5 before 4.0.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 4.0.5 up to, but not including, 4.0.10 are affected, and only where a Fastify route and an Express middleware mount share a dynamic path pattern. To check, look at the installed @fastify/express version in package.json or the lockfile, and review whether any routes and middleware mounts share a dynamic pattern.
Source: github.com
How do I fix CVE-2026-124626?
Upgrade @fastify/express to 4.0.10 or later, which is the listed fixed version for this vulnerability.
Source: github.com
Related
- CVE-2026-133120@fastify/express vulnerable to path-scoped middleware bypass via request URL decoding and normalization mismatches
- CVE-2026-129504@fastify/express vulnerable to path-scoped middleware bypass via prefix and mount path join mismatch
- 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.