Denial of service in @fastify/busboy via oversized URL-encoded fields
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- 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 are affected. The url-encoded parser can skip its per-field size check when a malformed percent escape makes the decoded length jump past the limit (CWE-400). An unauthenticated remote attacker can send a single url-encoded field or field name that buffers up to the whole request body in memory, regardless of the configured per-field limit.
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 and url-encoded form data used by Fastify. In versions 1.0.0 through 3.2.5, the url-encoded parser stops accumulating a field only when the decoded length exactly equals the configured per-field size limit, and a malformed percent escape is passed through verbatim by the decoder, so the decoded length can jump from just below the limit to just above it and skip that equality check. The parser then keeps buffering the field in memory until the next delimiter or the end of the request, so a single unauthenticated url-encoded field or field name can grow to the size of the whole request body regardless of a much smaller configured per-field limit, with memory use bounded only by the independent whole-request body limit. The issue is fixed in @fastify/busboy 3.2.6, which clamps a field as soon as the decoded length reaches or exceeds the limit, and users should upgrade to 3.2.6 or later. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.
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 3.2.6, which clamps a field once its decoded length reaches or exceeds the limit. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.
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-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-128842
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