Fastify Express path-scoped middleware bypass in case-insensitive routing
Only affects @fastify/express 4.0.0 through 4.0.9 when Fastify routing is set to caseSensitive: false and the mount path contains the letter k. Fixed in 4.0.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.10
- Who is exposed
- Specific setups only
Summary
A remote, unauthenticated attacker can reach a handler in @fastify/express that authentication, authorization, or rate-limiting middleware was meant to protect, by sending a request path that uses a Unicode look-alike character. This works only when the application enables case-insensitive routing and the mount path contains a letter that the router folds to ASCII.
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, when Fastify routing is configured to be case-insensitive, the router folds the request path to lower case in a way that maps certain non-ASCII Unicode characters to ASCII letters, but @fastify/express matches Express mount paths against the decoded path without applying the same folding. The two disagree, so a request that spells a letter of a mount path with an equivalent Unicode character is routed to the protected handler while the path-scoped middleware mounted on that path never matches and is skipped. An unauthenticated client can therefore reach a handler that an authentication, authorization, or rate-limiting middleware was meant to protect, though only when the application enables case-insensitive routing and the mount path contains an affected letter. 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.0 to 4.0.9 with case-insensitive Fastify routing and path-scoped auth, authorization or rate-limit middleware on mount paths containing k.
Not fixed by: Relying solely on path-scoped Express middleware leaves the route unprotected.
“Only a mount path containing k is affected, and only when the application enables caseSensitive: false”
What to do
Check whether your setup matches what the bug needs.
Fastify routing is case-insensitive (routerOptions.caseSensitive: false) The mount path contains the letter k Affected versions are 4.0.0 through 4.0.9 of @fastify/expressUpgrade 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-129850 (@fastify/express vulnerable to path-scoped middleware bypass via Unicode case folding), 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-129850 (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):
- Fastify routing is case-insensitive (routerOptions.caseSensitive: false) (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-6rmc-f24g-hmp6)
- The mount path contains the letter k (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-6rmc-f24g-hmp6)
- Affected versions are 4.0.0 through 4.0.9 of @fastify/express (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-6rmc-f24g-hmp6)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129850 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129850 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-6rmc-f24g-hmp6
- 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-129850
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-129850"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects npm packages
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
Impact
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/fastify-express · Advisory GHSA-6rmc-f24g-hmp6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129850 |
| Record | NVD · CVE-2026-129850 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-129850
Is CVE-2026-129850 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, can be skipped for a mount path when a client spells a k in it, so an unauthenticated client can reach the handler that middleware was meant to protect.
Source: github.com
Which versions are affected by CVE-2026-129850?
@fastify/express (npm): from 4.0.0 before 4.0.10.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are @fastify/express versions 4.0.0 through 4.0.9, and only when the application sets routerOptions.caseSensitive to false and has a mount path containing the letter k. To check, look at the installed @fastify/express version in the lockfile or with npm ls @fastify/express, and at the routerOptions.caseSensitive setting and mount paths in the application.
Source: github.com
How do I fix CVE-2026-129850?
Upgrade @fastify/express to version 4.0.10 or later, which is the listed fixed version.
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-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
No corrections so far. Something wrong on this page? Report an error.