# CVE-2026-128835: @fastify/busboy vulnerable to Denial of Service via a multipart part with unterminated headers

> Unauthenticated attackers can hang Fastify handlers with unterminated multipart headers, leaking resources until restart; Fastify apps using @fastify/busboy should care.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 17 Nov 2026
- **Also known as:** GHSA-pvmq-3jr9-v5qh, UBUNTU-CVE-2026-128835

## What is CVE-2026-128835?

CVE-2026-128835 is a high-severity denial of service 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 1.0.0 through 3.2.5, a multipart part whose header block is never terminated before the next boundary is counted by the vendored Dicer parser as an open part that never ends, so the parser emits neither a finish nor an error event and the request hangs. A single unauthenticated request of roughly one hundred bytes triggers the stall, and through @fastify/multipart the hung handler is not released when the client disconnects, so repeated requests leak handlers and whatever resources they hold, such as files, database connections and concurrency slots, until the process is restarted. The same parser is reached by the formData methods of undici versions 5.25.3 through 6.7.0. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. As a workaround, configure Fastify's handler timeout so hung handlers are eventually terminated and their resources released.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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` | All versions | 3.2.6 |

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

Upgrade %40fastify/busboy to 3.2.6 or later.

## Is CVE-2026-128835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128835 is a high-severity denial of service 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-128835 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 all versions; 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-128835/ (Markdown: https://insights.sbomify.com/CVE-2026-128835/index.md)
```

## Sources

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

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