CVE-2026-124289
@fastify/multipart vulnerable to arbitrary file write via type confusion in saveRequestFiles()
Description
@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 7.4.0 through 10.1.8, when the plugin is registered with the attachFieldsToBody option, the saveRequestFiles helper treats any object in the parsed request body that carries truthy file and buffer properties as an uploaded file. An unauthenticated client can forge such an object through a plain JSON request or a JSON-typed multipart field, so attacker-chosen bytes are written to the temporary directory while upload hooks and the file count and size limits are skipped, and the saved entry keeps the attacker's filename verbatim instead of being reduced to its basename. Because that filename can contain parent directory segments, applications that use it as a write destination, as the project README example does, are exposed to an arbitrary relative-path file write from a single request. The issue is fixed in @fastify/multipart 10.1.9, and users should upgrade to 10.1.9 or later. As a workaround, call saveRequestFiles only after confirming the request is multipart, and reduce each returned filename to its basename or validate it against an allowlist before using it as a destination.
INFO
Published Date :
Nov. 16, 2026, 1:09 p.m.
Last Modified :
Nov. 16, 2026, 1:09 p.m.
Remotely Exploit :
No
Source :
openjs
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | ce714d77-add3-4f53-aff5-83d477b104bb | ||||
| CVSS 3.1 | HIGH | MITRE-CVE |
Solution
- Upgrade @fastify/multipart to version 10.1.9 or later.
- Validate filenames against an allowlist before use.
- Reduce filenames to basenames before writing.
- Confirm requests are multipart before saving files.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-124289 vulnerability anywhere in the article.