CVE-2026-128842: @fastify/busboy vulnerable to Denial of Service via URL-encoded field size-limit bypass
@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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@fastify/busboyto a version that resolves this vulnerability.Fixed in 3.2.6 - Configuration
Set a conservative whole-request body limit to bound memory use from an oversized URL-encoded field.
@fastify/busboy whole-request body limit = conservative limit
Event History
Frequently Asked Questions
Who can trigger this denial of service?
An unauthenticated remote client can trigger it by sending a crafted URL-encoded request containing a single oversized field or field name. No user interaction or privileges are required.
Are installations affected if a per-field size limit is configured?
Yes. The flaw bypasses the configured per-field limit when decoded length skips over the exact limit value, allowing the parser to continue buffering data. Memory consumption is instead bounded by the independent whole-request body limit.
What can be done before upgrading?
Set a conservative whole-request body limit to cap the maximum memory consumed by an oversized URL-encoded field. This limits the possible per-field overshoot until @fastify/busboy can be upgraded.
Which versions need remediation?
Versions 1.0.0 through 3.2.5 are affected. Upgrade to version 3.2.6 or later, which enforces the field limit when decoded length reaches or exceeds it.