---
id: "CVE-2026-128846"
page: "https://infrastack.ai/live/CVE-2026-128846"
kind: "vulnerability"
aliases: ["CVE-2026-128846"]
title: "@fastify/busboy: split multipart headers let uploads bypass file-event validation"
severity: "low"
cvss: 3.7
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["fastify", "node", "package", "self-hosted"]
not_affected_if: ["no-multipart-uploads", "validates-all-parts"]
published_at: "2026-11-16T14:17:06+00:00"
first_seen_at: "2026-11-16T14:36:59+00:00"
updated_at: "2026-11-16T14:37:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-128846", "first_seen_at": "2026-11-16T14:36:59+00:00"}]
exploit_sources: []
---

# @fastify/busboy: split multipart headers let uploads bypass file-event validation

Link for people: https://infrastack.ai/live/CVE-2026-128846 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version with `npm ls @fastify/busboy` in the project.
- Look for `@fastify/busboy` versions `3.2.1` through `3.2.5` in the lockfile.
- Find which apps use Fastify multipart uploads and check whether they validate only file events.

## Fix

- @fastify/busboy: upgrade to `3.2.6` or later.
- Workaround from the sources: apply the same validation to field values as to file uploads.

## Timeline

- 2026-11-16T14:36:59+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-128846

## Documents

- [advisory] Vendor advisory: github.com https://github.com/fastify/busboy/security/advisories/GHSA-2q57-jvxc-h47j

## From the sources

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

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
