# CVE-2026-128846: @fastify/busboy vulnerable to multipart file/field type confusion via chunk-dependent header parsing

> Remote clients can send multipart data that bypasses upload validation like malware scanning or extension checks in Fastify apps using @fastify/busboy.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-2q57-jvxc-h47j, UBUNTU-CVE-2026-128846

## What is CVE-2026-128846?

CVE-2026-128846 is a low-severity security feature bypass vulnerability in @fastify/busboy, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2026-128846?

1 open source package ship an affected version, including %40fastify/busboy.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `%40fastify/busboy` | npm | `pkg:npm/%40fastify/busboy` | From 3.2.1 | 3.2.6 |

## How do I fix CVE-2026-128846?

Upgrade %40fastify/busboy to 3.2.6 or later.

## Is CVE-2026-128846 being exploited?

There is no known exploitation of CVE-2026-128846 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128846 and fix it if it is affected.

What it is: CVE-2026-128846 is a low-severity security feature bypass vulnerability in @fastify/busboy, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-128846 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- %40fastify/busboy (npm): affected from 3.2.1; fixed in 3.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128846/ (Markdown: https://insights.sbomify.com/CVE-2026-128846/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128846
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128846
- OSV: https://osv.dev/vulnerability/CVE-2026-128846

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128846/
Summaries are generated and may contain mistakes; the official description above is the record.
