Skip to content
Fencer Intel
medium 5.3

CVE-2026-128842 json

@fastify/busboy vulnerable to Denial of Service via URL-encoded field size-limit bypass

published yesterday modified 10h ago also EUVD-2026-126377 , GHSA-x578-65c5-rvww

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository fastify/busboy. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

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

Patch / fix

  • npm @fastify/busboy 3.2.6
  • @fastify/busboy @fastify/busboy 3.2.6

Is CVE-2026-128842 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
11h ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-17).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm @fastify/busboy
<3.2.6
3.2.6

Affected products

  • @fastify/busboy @fastify/busboy

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of fastify/busboy published their own advisory on GitHub. Reviewed sources take precedence over it.