CVE-2026-124289: @fastify/multipart · Path Traversal
Affects @fastify/multipartSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 10.1.9 soon.
Data as of 16 Nov 2026, 13:50 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 10.1.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 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 15 Nov 2026.
What to do
Upgrade @fastify/multipart to 10.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/multipart@fastify/multipart | Affected
| Fixed in
|
npm@fastify/multipartpkg:npm/@fastify/multipartOther 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 to @fastify/multipart version 10.1.9 or later where the vulnerability is fixed. As a workaround, only call saveRequestFiles after confirming the request is multipart, and sanitize or validate filenames by reducing them to their basename or checking against an allowlist before using them as write destinations.
Description
@fastify/multipart versions 7.4.0 through 10.1.8 contain a path traversal vulnerability when used with the attachFieldsToBody option. An unauthenticated attacker can craft a JSON or JSON-typed multipart request that causes arbitrary files to be written to the server's temporary directory with attacker-controlled filenames, including directory traversal sequences. This occurs because the plugin treats objects with truthy file and buffer properties as uploaded files and does not sanitize filenames. The vulnerability is fixed in version 10.1.9.