# CVE-2026-128842: @fastify/busboy vulnerable to Denial of Service via URL-encoded field size-limit bypass

> Unauthenticated attackers can bypass per-field size limits with url-encoded fields to exhaust memory in Fastify apps using @fastify/busboy.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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-x578-65c5-rvww, UBUNTU-CVE-2026-128842

## What is CVE-2026-128842?

CVE-2026-128842 is a medium-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 and url-encoded form data used by Fastify. In versions 1.0.0 through 3.2.5, the url-encoded parser stops accumulating a field only when the decoded length exactly equals the configured per-field size limit, and a malformed percent escape is passed through verbatim by the decoder, so the decoded length can jump from just below the limit to just above it and skip that equality check. The parser then keeps buffering the field in memory until the next delimiter or the end of the request, so a single unauthenticated url-encoded field or field name can grow to the size of the whole request body regardless of a much smaller configured per-field limit, with memory use bounded only by the independent whole-request body limit. The issue is fixed in @fastify/busboy 3.2.6, which clamps a field as soon as the decoded length reaches or exceeds the limit, and users should upgrade to 3.2.6 or later. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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-128842?

Upgrade %40fastify/busboy to 3.2.6 or later.

## Is CVE-2026-128842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128842 is a medium-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-128842 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-128842/ (Markdown: https://insights.sbomify.com/CVE-2026-128842/index.md)
```

## Sources

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

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