Denial of service in @fastify/busboy via unterminated multipart headers
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-400.
Summary
@fastify/busboy versions 1.0.0 through 3.2.5 contain a flaw in the vendored Dicer multipart parser, which counts a part with unterminated headers as an open part that never ends, causing CWE-400 (Uncontrolled Resource Consumption). A single unauthenticated request of roughly one hundred bytes makes the parser emit neither a finish nor an error event, so the request hangs. Through @fastify/multipart, hung handlers are not released when the client disconnects, so repeated requests leak handlers and their resources until the process restarts. The formData methods of undici versions 5.25.3 through 6.7.0 reach the same parser.
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, 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade @fastify/busboy to version 3.2.6 or later, which fixes this issue. As a workaround, configure Fastify's handler timeout so hung handlers are terminated and their resources released.
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-92123 Denial of service in @fastify/busboy via oversized URL-encoded fieldsPriority LOW 39
- TI-2026-92121 Crash in @fastify/busboy multipart parser on truncated requestPriority LOW 36
- 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-128835
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