CVE-2026-110710 · Package
NO FIX YET · SEE WHAT TO DO
When a client finishes an upload and disconnects before the handler replies, saveRequestFiles temp files are never cleaned up. An unauthenticated client can repeat this to fill the disk and deny service.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications built on Fastify that use @fastify/multipart with saveRequestFiles to write uploaded files to disk are exposed. Applications that do not save request files, or that only accept uploads from trusted clients, are less exposed. The workaround stated in the sources is to avoid saving request files for untrusted clients, or to clean saved files from a close handler on the raw response.
Not affected if no-saverequestfiles, trusted-clients-only, version-10.1.4-or-later
Who cares fastify, file-uploads, node, self-hosted
npm ls @fastify/multipart and compare it against the fixed release.saveRequestFiles in the application code.@fastify/multipart 10.1.4 or later.@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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.