CVE-2026-110710: @fastify/multipart vulnerable to Denial of Service via temporary file leak after client disconnect

Published Nov 16, 2026
·
Updated

@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.

Affected Software

1 affected component
npm/@fastify/multipart>=3.0.0<=10.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade @fastify/multipart to a version that resolves this vulnerability.

    Fixed in 10.1.4
  2. Compensating control

    Avoid saving request files for untrusted clients.

  3. Compensating control

    Clean up saved files from a close handler on the raw response so they are removed when the client disconnects.

Event History

Nov 16, 2026
CVE Published
via MITRE·01:03 PM
Data Sourced
via MITRE·01:03 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using @fastify/multipart versions 3.0.0 through 10.1.3 are exposed if they use the saveRequestFiles helper to write uploads to disk. The risk is especially relevant where untrusted clients can submit multipart uploads.

2

What does an attacker need to do to trigger the denial of service?

No authentication or user interaction is required. An attacker can complete an upload and disconnect before the application handler writes its reply, then repeat the process to leave temporary files on disk until storage is exhausted.

3

What can be done if upgrading is not immediately possible?

Avoid saving request files for untrusted clients, or add cleanup from a close handler on the raw response. This ensures saved files are removed when a client disconnects rather than only when the response finishes or errors.

4

How can teams determine whether they are affected?

Check whether the application uses saveRequestFiles and runs @fastify/multipart from version 3.0.0 through 10.1.3. Systems may also show accumulating temporary upload files after clients disconnect before request handlers send a response.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203