CVE-2026-129504: @fastify/express · Interpretation Conflict
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
Users should upgrade @fastify/express to version 4.0.10 or later, where the issue is fixed. No other mitigation is required as the fix addresses the root cause.
Description
@fastify/express versions 4.0.0 through 4.0.9 contain a vulnerability where path-scoped Express middleware mount paths are concatenated improperly with Fastify plugin prefixes. This causes a mismatch between the Express mount path and the Fastify route, resulting in Express middleware being silently skipped. Applications using such middleware for authentication or authorization may expose protected routes to unauthenticated clients. The issue is fixed in version 4.0.10.