CVE-2026-129850
@fastify/express vulnerable to path-scoped middleware bypass via Unicode case folding
No exploitation reported by the sources we read.
- Published2026-11-21
- WeaknessCWE-178 · CWE-863
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-2117:05CVE publishedCNA
Versions per branch
Products declared by the CNA
As openjs, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- @fastify/expressother versions: not affectedAffected
- ≥ 4.0.0, < 4.0.10fixed in 4.0.10semver
Not affected = 4.0.10
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-21
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-129850 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2026-11-21
- Last modified
- 2026-11-21
- NVD status
- Received
Frequently asked questions
What is CVE-2026-129850?
Is CVE-2026-129850 actively exploited?
What is the CVSS score for CVE-2026-129850?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.