Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
CVE-2026-128846: @fastify/busboy may treat uploaded files as plain fields
CVE-2026-128846 · published 6 days ago
Summary
Versions 3.2.1 through 3.2.5 of the @fastify/busboy component can misinterpret a file upload as a simple text field when the data arrives in a particular split pattern. This can let a malicious client bypass checks that are only applied to file uploads, such as virus scanning or file‑type validation. Upgrade to version 3.2.6 or later, or apply the same validation to all incoming data, to resolve the risk.
What to do
- Update @fastify/busboy @fastify/busboy to version 3.2.6 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | @fastify/busboy | @fastify/busboy | < 3.2.6 |
| Ubuntu:24.04:LTS | canonical | node-undici | All versions |
Original advisory text
@fastify/busboy vulnerable to multipart file/field type confusion via chunk-dependent header parsing
@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.
References
- https://cna.openjsf.org/security-advisories.html Vendor Advisory
- https://github.com/fastify/busboy/security/advisories/GHSA-2q57-jvxc-h47j Vendor Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-1288... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-128846 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-128846 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-128846 Third Party Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-193Off-by-one Error
Timeline
Published16 Nov 2026
Updated22 Nov 2026
First seen16 Nov 2026
Sources
CVE-2026-128846 · NVD
CVE-2026-128846 · MITRE
CVE-2026-128846 · OSV
GHSA-2q57-jvxc-h47j · GHSA
UBUNTU-CVE-2026-128846 · OSV
Track software like this
Free during beta