CVE-2026-133120: @fastify/express · Double Decoding of the Same Data
Affects @fastify/expressSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.0.10 as a priority.
Data as of 21 Nov 2026, 17:14 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 9.1 |
|---|
- Patch
- Available – fixed in 4.0.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade @fastify/express to 4.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/express@fastify/express | Affected
| Fixed in
|
npm@fastify/expresspkg:npm/@fastify/expressOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @fastify/express to version 4.0.10 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause of the URL mismatch and middleware bypass.
Description
@fastify/express versions before 4.0.10 have a vulnerability where the request URL passed to Express middleware can differ from the path dispatched by Fastify's router. This mismatch occurs due to double decoding of encoded characters and special request targets, causing path-scoped middleware like authentication or rate-limiting to be bypassed. An unauthenticated attacker can exploit this to reach protected route handlers without triggering middleware protections. The issue is fixed in version 4.0.10.