CVE-2026-124724: @fastify/busboy vulnerable to Denial of Service via truncated multipart part past the parts limit
@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, when a request reaches the configured limit on the number of multipart parts, each further part is skipped without attaching an error listener to the skipped part stream. If the request body ends in the middle of such a skipped part, the vendored Dicer parser emits an error on that stream, and because nothing is listening Node.js raises an unhandled error event and the process exits. A single crafted unauthenticated request is therefore enough to crash the server. The bug is latent in the parser on its own and was first demonstrated through @fastify/multipart versions 10.1.2 through 10.1.4, which keep feeding the request body to the parser after a limit error, and it affects any consumer that sets a finite parts limit and parses request bodies that can be terminated early. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. There is no complete application level workaround because the crash happens inside the parser before application code runs, though consumers that set a finite parts limit should also attach an error listener to the parser stream.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@fastify/busboyto a version that resolves this vulnerability.Fixed in 3.2.6 - Compensating control
For consumers that set a finite parts limit, attach an error listener to the parser stream.
Event History
Frequently Asked Questions
Which deployments are exposed to this denial-of-service condition?
Affected deployments use @fastify/busboy versions 1.0.0 through 3.2.5, configure a finite multipart parts limit, and parse request bodies that can terminate early. The issue was demonstrated through @fastify/multipart 10.1.2 through 10.1.4, which continue feeding the request body after a limit error.
What does an attacker need to do to trigger the crash?
An attacker can send a single unauthenticated multipart request that exceeds the configured parts limit and then ends in the middle of a subsequently skipped part. This causes an unhandled error event in Node.js, terminating the process.
Does this require application code to process the malformed part?
No. The failure occurs inside the parser before application code runs, so application-level handling is not a complete workaround.
What should be done if an immediate upgrade is not possible?
There is no complete application-level workaround. Consumers that use a finite parts limit should attach an error listener to skipped part streams, but upgrading @fastify/busboy to 3.2.6 or later is the stated fix.