Live › vulnerability › CVE-2026-117531
A malformed multipart upload with no closing boundary makes the Fastify multipart plugin drop the file stream without an error, so handlers that consume the file later never finish. An unauthenticated remote client can repeat these requests to pile up open connections and exhaust server resources.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 11:22 UTC. All times on this page are UTC.
Applications built on Fastify that use @fastify/multipart versions 5.3.0 through 10.1.6 to accept file uploads, where a route handler delays reading the file stream. Routes that consume files immediately, or applications not using the multipart plugin, are not exposed to the hang.
No product ranges from the sources yet.
npm ls @fastify/multipartrequest.parts() or request.file() and do asynchronous work before reading the file stream@fastify/multipart 10.1.7 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
@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.
This page as .md · .json · in your agent: get_signal("CVE-2026-117531")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.