CVE-2026-128842 · Package
NO FIX YET · SEE WHAT TO DO
@fastify/busboy is a form parser used by Fastify. A malformed percent escape in a url-encoded form field makes the per-field size limit fail to stop buffering, so one unauthenticated field can grow to the whole request body size and use a lot of memory.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that use @fastify/busboy from 1.0.0 through 3.2.5 to parse url-encoded form bodies, typically through Fastify, are exposed. Exposure is reached through any unauthenticated request that sends a url-encoded field with a malformed percent escape. Apps that do not parse url-encoded forms, or that already run a tight whole-request body limit, are less exposed.
Not affected if auth-required, no-urlencoded-forms
Who cares fastify, node, self-hosted
npm ls @fastify/busboy; versions from 1.0.0 through 3.2.5 are affected.@fastify/busboy 3.2.6 or later@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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.