CVE-2026-128835: @fastify/busboy vulnerable to Denial of Service via a multipart part with unterminated headers
@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, a multipart part whose header block is never terminated before the next boundary is counted by the vendored Dicer parser as an open part that never ends, so the parser emits neither a finish nor an error event and the request hangs. A single unauthenticated request of roughly one hundred bytes triggers the stall, and through @fastify/multipart the hung handler is not released when the client disconnects, so repeated requests leak handlers and whatever resources they hold, such as files, database connections and concurrency slots, until the process is restarted. The same parser is reached by the formData methods of undici versions 5.25.3 through 6.7.0. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. As a workaround, configure Fastify's handler timeout so hung handlers are eventually terminated and their resources released.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@fastify/busboyto a version that resolves this vulnerability.Fixed in 3.2.6 - Configuration
Configure a handler timeout so hung handlers are eventually terminated and their resources released.
Fastify handler timeout
Event History
Frequently Asked Questions
Which applications are exposed to this denial-of-service issue?
Applications using @fastify/busboy versions 1.0.0 through 3.2.5 to parse multipart form data are affected. The vulnerable parser is also reachable through @fastify/multipart, and through the formData methods in undici versions 5.25.3 through 6.7.0.
Does exploitation require authentication or a large request?
No. A remote unauthenticated attacker can trigger the condition with a single malformed multipart request of roughly one hundred bytes.
What is the operational impact of repeated exploitation?
Each malformed request can leave a handler hung without emitting a finish or error event. When reached through @fastify/multipart, disconnecting the client does not release that handler, so repeated requests can exhaust held resources such as files, database connections, and concurrency slots until the process is restarted.
What should be done if upgrading cannot happen immediately?
Configure Fastify's handler timeout so that hung handlers are eventually terminated and their resources are released. The stated permanent fix is upgrading @fastify/busboy to version 3.2.6 or later.