CVE-2026-124289
7.5HighPublished 16 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on integrity
- Weakness
- CWE-22, CWE-843
What an attacker gets
Unauthenticated attackers can perform arbitrary file writes on the server by crafting malicious JSON or multipart requests. This bypasses file size and count limits, allowing attackers to overwrite files if the application uses the provided filename directly.
Root cause
The saveRequestFiles helper incorrectly trusts user-supplied objects and filenames, failing to sanitize directory traversal sequences.
Affected versions
@fastify/multipart versions 7.4.0 through 10.1.8
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Fix & remediation
Upgrade to @fastify/multipart 10.1.9 or later. If you cannot upgrade, sanitize all filenames returned by saveRequestFiles using path.basename() or an allowlist before using them as file paths.
$ npm install @fastify/multipart@latestAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.