CVE-2026-128846 · Package
NO FIX YET · SEE WHAT TO DO
A multipart parser bug in @fastify/busboy can treat a binary file attachment as a plain text field when the header terminator is split at the header size limit. An application that scans or checks only file events may then process the upload without those checks.
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 built on Fastify that accept multipart form uploads through @fastify/busboy versions 3.2.1 to 3.2.5. The exposure depends on the application: if upload validation such as malware scanning or extension checks runs only on file events and trusts plain field values, a crafted request can route a file through the field path. Apps that do not accept multipart uploads, or that validate every part regardless of type, are less exposed.
Not affected if no-multipart-uploads, validates-all-parts
Who cares fastify, node, self-hosted
npm ls @fastify/busboy in the project.@fastify/busboy versions 3.2.1 through 3.2.5 in the lockfile.3.2.6 or later.@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 3.2.1 through 3.2.5, the parser can interpret the same multipart bytes differently depending on how they are split across socket reads: when the sequence that terminates a part's header block arrives split exactly at the configured header size limit, an off by one error drops the final header line, so a part declared as a binary file attachment is emitted as an ordinary text field instead of a file. A remote client controls both the multipart body and the header padding needed to reach the boundary and can influence segmentation, so an application that applies upload validation such as malware scanning or extension checks only to file events while trusting plain field values may process the payload through the wrong path. The parser level type confusion is fully reproducible, while the downstream validation bypass depends on the application. The issue is fixed in @fastify/busboy 3.2.6, which tracks how many terminator bytes were actually buffered when the limit is reached so a split terminator no longer corrupts the final header, and users should upgrade to 3.2.6 or later. As a workaround, apply the same validation to field values as to file uploads rather than treating file events as a trust boundary.
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.