Fastify Express auth bypass in path-scoped middleware via prefix mismatch
Affects @fastify/express 4.0.0 before 4.0.10 when path-scoped middleware is used inside prefixed Fastify plugins. 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 silently skip path-scoped middleware when a plugin prefix ends with a slash or a mount path lacks its leading slash. A remote attacker without logging in can then reach protected routes, including those guarded by authentication or authorization middleware.
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.0 through 4.0.9, the plugin joins a path-scoped middleware's mount path to the Fastify plugin prefix by string concatenation, so when the plugin prefix ends with a slash or the mount path omits its leading slash, the resulting Express mount path does not line up with the route the Fastify router serves. Express then fails to match and passes the request on while the Fastify router still dispatches the route, so the middleware is silently skipped. An application that uses path-scoped Express middleware for authentication or authorization inside a prefixed plugin can expose protected routes to unauthenticated clients, with no crafted request and no non-default option required, and string, array, and regular-expression mount paths are all affected. 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 before 4.0.10 that use path-scoped Express middleware for authentication or authorization inside prefixed Fastify plugins
“Applications that use path-scoped Express middleware for authentication or authorization inside prefixed Fastify plugins”
What to do
Check every install: default setups are affected.
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-129504 (@fastify/express vulnerable to path-scoped middleware bypass via prefix and mount path join mismatch), 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-129504 (entry last updated 2026-11-21):
Affected:
- npm package @fastify/express: from 4.0.0, fixed in 4.0.10
Fixed versions: 4.0.10.
Conditions (all must be true for the bug to be hit):
- Path-scoped middleware mounted inside a Fastify plugin with a prefix that ends in a slash, or a mount path given without a leading slash (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-f44m-4qwg-5587)
- Application uses path-scoped Express middleware for authentication or authorization inside prefixed Fastify plugins (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-f44m-4qwg-5587)
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.
CISA KEV: CVE-2026-129504 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129504 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-f44m-4qwg-5587
- 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-129504
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-129504"}.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-f44m-4qwg-5587 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129504 |
| Record | NVD · CVE-2026-129504 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-129504
Is CVE-2026-129504 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 or authorization checks, can be silently skipped, so unauthenticated clients can reach protected routes.
Source: github.com
Which versions are affected by CVE-2026-129504?
@fastify/express (npm): from 4.0.0 before 4.0.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 4.0.0 before 4.0.10 are affected. The setup involves path-scoped Express middleware inside prefixed Fastify plugins, where the plugin prefix ends with a slash or the mount path passed to use() lacks a leading slash. To check a project, look at the installed @fastify/express version (for example with npm ls @fastify/express) and review where use() is called inside prefixed plugins.
Source: github.com
How do I fix CVE-2026-129504?
Upgrade @fastify/express to 4.0.10 or later.
Source: github.com
Related
- CVE-2026-133120@fastify/express vulnerable to path-scoped middleware bypass via request URL decoding and normalization mismatches
- 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.