CVE-2026-117531: @fastify/multipart vulnerable to Denial of Service via a malformed upload hanging delayed file consumers

Published Nov 2, 2026
·
Updated

@fastify/multipart is the multipart form-data and file upload plugin for the Fastify web framework. In versions 5.3.0 through 10.1.6, the plugin does not propagate a parser error to the file stream when a request body ends inside a file part with no closing boundary, even though the Content-Length is complete, the client does not abort, and no file size limit is exceeded. The plugin destroys the in-progress file stream without an error, so a handler that iterates the request parts and performs asynchronous work before consuming the file attaches to a stream that never emits an error or end event, and the request never responds while the connection stays open. An unauthenticated remote client can repeat these malformed uploads against such a route to accumulate pending connections and exhaust server resources, so the impact is availability only and exploitation depends on the application using a delayed file consumer. The issue is fixed in @fastify/multipart 10.1.7, where the parser error is propagated to the file stream so a delayed consumer settles with an error instead of hanging, and users should upgrade to 10.1.7 or later. There is no workaround other than upgrading.

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

Event History

Nov 2, 2026
CVE Published
via OSV·10:32 AM
Data Sourced
via OSV·10:32 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this denial-of-service condition?

Applications using @fastify/multipart versions 5.3.0 through 10.1.6 are exposed only if an upload route performs asynchronous work after iterating request parts but before consuming the file stream. The delayed consumer can then wait indefinitely when given a malformed multipart upload.

2

Does exploitation require authentication or exceeding configured upload limits?

No. An unauthenticated remote client can trigger the issue with a request body that ends inside a file part without a closing boundary; the stated condition does not require a client abort or exceeding a file size limit.

3

What is the operational impact of a successful attack?

Affected requests can remain open without responding, allowing repeated malformed uploads to accumulate pending connections and exhaust server resources. The described impact is limited to availability.

4

How can this be remediated or mitigated?

Upgrade @fastify/multipart to version 10.1.7 or later, which propagates the parser error to the file stream so delayed consumers settle with an error. No workaround other than upgrading is provided.

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