CVE-2026-124724 · Package
NO FIX YET · SEE WHAT TO DO
@fastify/busboy, the multipart form parser used by Fastify, versions 1.0.0 through 3.2.5, leaves an error listener off skipped parts once a parts limit is hit. A single unauthenticated request whose body ends mid-part makes Node.js raise an unhandled error and exit, crashing the server.
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 that use @fastify/busboy directly or through @fastify/multipart and accept multipart form uploads with a finite parts limit are exposed, because the crash happens inside the parser before application code runs. Services that do not parse multipart bodies, or that run a version at or above 3.2.6, are not affected. The sources say there is no complete application-level workaround, though attaching an error listener to the parser stream is advised for consumers that set a finite parts limit.
Not affected if no-multipart-parsing, version-3.2.6-or-later
Who cares fastify, multipart, node.js, npm
npm ls @fastify/busboy in the project to find the installed version.@fastify/multipart is in use at versions 10.1.2 through 10.1.4.3.2.6 or later.@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.
This page as ·
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.