Crash in @fastify/busboy multipart parser on truncated request
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-248.
Summary
@fastify/busboy from 1.0.0 before 3.2.6 is affected. After the configured parts limit is reached, skipped parts get no error listener, so a request body that ends in the middle of one raises an unhandled error that exits the process (CWE-248). An unauthenticated remote attacker can crash the server with a single crafted request.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
@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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade @fastify/busboy to 3.2.6, which fixes the issue. Applications that set a finite parts limit should also attach an error listener to the parser stream.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA @fastify/busboy (@fastify/busboy) Fixed in 3.2.6
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
@fastify/busboy 3.2.6
4 records Highest priority Priority MEDIUM 1 MEDIUM, 3 LOW
Other records, highest priority first
- TI-2026-92122 Denial of service in @fastify/busboy via unterminated multipart headersPriority MEDIUM 48
- TI-2026-92123 Denial of service in @fastify/busboy via oversized URL-encoded fieldsPriority LOW 39
- TI-2026-92124 Off-by-one error in @fastify/busboy misparses multipart file partsPriority LOW 15
Timeline
- 2026-11-16 Threatist record created from CVE-2026-124724
- 2026-11-16 CISA SSVC decision points changed
References
More fastify vulnerabilities
- TI-2026-26180 @fastify/express vulnerable to middleware authentication bypass via URL normalization… CVSS 4.0CRITICAL 9.1
- TI-2026-26179 @fastify/express vulnerable to middleware path doubling causing authentication bypass in child plugin scopes CVSS 3.1CRITICAL 9.1
- TI-2026-26177 @fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers CVSS 4.0CRITICAL 9.0
- TI-2026-05498 @fastify/middie vulnerable to middleware authentication bypass in child plugin scopes CVSS 3.1CRITICAL 9.1
- TI-2023-15307 Cross-site request forgery in npm @fastify/oauth2 CVSS 3.1HIGH 8.8
- TI-2022-18664 Denial of service in Fastify via Content-Type header CVSS 3.1HIGH 7.5
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences