Skip to main content
Menu
CVEs

CVE

Fastify Busboy denial of service in multipart parser

Affects @fastify/busboy from 1.0.0 up to 3.2.5 when a multipart part's header block is never terminated before the next boundary. Fixed in 3.2.6.

CVE-2026-128835EUVD-2026-126376

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.6
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.2.6.

Published
Last modified
Reference
Last checked
45/100 · provisional
Unclear
100% of @fastify/busboy downloads last week were affected versions (51.4M).npm, 51.4M downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub

Summary

@fastify/busboy, a streaming parser for multipart form data, can be made to stall by a single remote, unauthenticated request of about one hundred bytes that contains a multipart part whose headers are never terminated, causing a denial of service. Repeated requests leak the hung handlers and the resources they hold until the process is restarted.

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

Who should check

Teams running @fastify/busboy 1.0.0 to 3.2.5, including Fastify apps using @fastify/multipart, and Node.js code using undici formData() on 5.25.3 to 6.7.0

Not fixed by: No workaround fully prevents the stall before parsing.

“Versions of @fastify/busboy from 1.0.0 and prior to 3.2.6 are vulnerable to a Denial of Service”

github.com

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach20/20@fastify/busboy: 51.4M downloads a week
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

Impact

  • Widely used

    @fastify/busboy has 51.4m weekly downloads.Source: npmjs.com

What to do

  • Upgrade to a fixed version: 3.2.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128835 (@fastify/busboy vulnerable to Denial of Service via a multipart part with unterminated headers), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128835 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/busboy: fixed in 3.2.6
Fixed versions: 3.2.6.
Conditions (all must be true for the bug to be hit):
- @fastify/busboy versions from 1.0.0 up to 3.2.5 (fixed in 3.2.6) (source: https://github.com/fastify/busboy/security/advisories/GHSA-pvmq-3jr9-v5qh)
- A multipart part whose header block is never terminated before the next boundary (source: https://github.com/fastify/busboy/security/advisories/GHSA-pvmq-3jr9-v5qh)
- Undici formData methods on versions 5.25.3 through 6.7.0 also reach the same parser (source: https://github.com/fastify/busboy/security/advisories/GHSA-pvmq-3jr9-v5qh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128835 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128835 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/busboy/security/advisories/GHSA-pvmq-3jr9-v5qh
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128835
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128835"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • fixed in 3.2.6

    Fixed in 3.2.6 (released Nov 16, 2026, the day of disclosure).

    The latest release, 3.2.6, is not affected.

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128835

Is CVE-2026-128835 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A multipart part whose header block is cut off by the next boundary is never completed, so the request hangs. Each such request leaks its handler and what it holds, such as files, database connections, and concurrency slots, until the process restarts, which causes denial of service.Source: github.com

Which versions are affected by CVE-2026-128835?

@fastify/busboy (npm): before 3.2.6.Source: cve.now feed data

Am I affected, and how do I check?

Versions of @fastify/busboy from 1.0.0 before 3.2.6 are affected. Undici's Response.formData() and Request.formData() in versions 5.25.3 through 6.7.0 also reach the same parser. Check the installed @fastify/busboy version in the dependency tree, for example with npm ls @fastify/busboy, and the installed undici version.Source: github.com

How do I fix CVE-2026-128835?

Upgrade @fastify/busboy to 3.2.6, the fixed version.Source: github.com