---
id: "CVE-2026-124724"
page: "https://infrastack.ai/live/CVE-2026-124724"
kind: "vulnerability"
aliases: ["CVE-2026-124724"]
title: "@fastify/busboy: crafted multipart request crashes Node.js server process"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["fastify", "multipart", "node.js", "npm", "package"]
not_affected_if: ["no-multipart-parsing", "version-3.2.6-or-later"]
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:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-124724", "first_seen_at": "2026-11-16T14:36:59+00:00"}]
exploit_sources: []
---

# @fastify/busboy: crafted multipart request crashes Node.js server process

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

@fastify/busboy, the multipart form parser used by Fastify, versions 1.0.0 through 3.2.5, leaves an error listener off skipped parts once a parts limit is hit. A single unauthenticated request whose body ends mid-part makes Node.js raise an unhandled error and exit, crashing the server.

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

## How to check

- Run `npm ls @fastify/busboy` in the project to find the installed version.
- Check whether `@fastify/multipart` is in use at versions `10.1.2` through `10.1.4`.
- Check whether the multipart parser is configured with a finite parts limit.

## Fix

- @fastify/busboy: upgrade to `3.2.6` or later.

## Timeline

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

## Documents

- [advisory] Vendor advisory: github.com https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3

## From the sources

@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, when a request reaches the configured limit on the number of multipart parts, each further part is skipped without attaching an error listener to the skipped part stream. If the request body ends in the middle of such a skipped part, the vendored Dicer parser emits an error on that stream, and because nothing is listening Node.js raises an unhandled error event and the process exits. A single crafted unauthenticated request is therefore enough to crash the server. The bug is latent in the parser on its own and was first demonstrated through @fastify/multipart versions 10.1.2 through 10.1.4, which keep feeding the request body to the parser after a limit error, and it affects any consumer that sets a finite parts limit and parses request bodies that can be terminated early. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. There is no complete application level workaround because the crash happens inside the parser before application code runs, though consumers that set a finite parts limit should also attach an error listener to the parser stream.

---

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