CVE-2026-110710
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 availability
- Weakness
- CWE-459, CWE-772
What an attacker gets
Unauthenticated attackers can exhaust disk space and cause a denial of service by repeatedly uploading files and disconnecting before the response finishes. This requires no prior access or user interaction.
Root cause
The plugin fails to trigger file cleanup when a client disconnects before the request handler completes.
Affected versions
@fastify/multipart versions 3.0.0 through 10.1.3
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Fix & remediation
Upgrade to @fastify/multipart 10.1.4 or later. If you cannot upgrade, implement a cleanup handler on the raw response 'close' event to remove temporary files.
$ 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 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response finishes or errors. When a client completes an upload and then disconnects before the handler writes the reply, for example while the handler scans, hashes or forwards the file, the response only emits a close event, the cleanup hook never runs, and the saved files are left on disk. An unauthenticated client can repeat this cheaply to exhaust disk space and deny service to applications that save uploaded files to disk. The issue is fixed in @fastify/multipart 10.1.4, and users should upgrade to 10.1.4 or later. As a workaround, avoid saving request files for untrusted clients, or clean the saved files from a close handler on the raw response so removal also happens when the client disconnects.