CVE-2026-128842

MEDIUMCVSS 5.3/10

Last modified

CVE-2026-128842 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. @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.

Description

@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.

Metrics

Weakness Enumeration

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
@fastify/busboy@fastify/busboy< 3.2.6

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-128842?
@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.
How severe is CVE-2026-128842?
CVE-2026-128842 has a CVSS score of 5.3/10 (MEDIUM severity).
How do I fix CVE-2026-128842?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-128842?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST