CVE-2026-128835 · Package
NO FIX YET · SEE WHAT TO DO
A single unauthenticated multipart request of about one hundred bytes makes the @fastify/busboy parser stall without finishing or erroring. Through @fastify/multipart, repeated requests leak hung handlers and the resources they hold until the process restarts, causing denial of service.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications built on Fastify that parse multipart form data with @fastify/busboy or @fastify/multipart are exposed, and so are applications using undici's formData methods in the affected range. Any internet-facing endpoint that accepts multipart uploads is reachable by a single unauthenticated request. Teams that do not accept multipart input or do not use these packages can skip it.
Not affected if no-multipart-endpoints, patched-version
Who cares fastify, node, self-hosted, undici
npm ls @fastify/busboy; versions 1.0.0 through 3.2.5 are affected.@fastify/multipart is used in the application, since it is the path that does not release hung handlers.@fastify/busboy 3.2.6@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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.