CVE
Fastify Busboy denial of service in multipart form parser
Affects @fastify/busboy 1.0.0 through 3.2.5 on routes that set a finite multipart parts limit and receive bodies that end mid-skipped-part. No vendor rating is given. Fixed in 3.2.6.
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
- 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.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 48/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- >99.9% of @fastify/busboy downloads last week were affected versions (51.4M).npm, 51.4M downloads in the last 7 days, read Nov 16, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The @fastify/busboy multipart form parser can be crashed remotely, without logging in, by a single crafted request whose body ends partway through a part after the parts limit is reached, which takes down the server. Applications that set a finite parts limit are affected, and because no complete application-level workaround exists, the fix is to upgrade to the patched release.
Original description
@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.
Who should check
Teams running @fastify/busboy 1.0.0 to 3.2.5, including Fastify apps using @fastify/multipart 10.1.2 to 10.1.4, and any consumer that sets a finite parts limit on request bodies that can end early.
Not fixed by: An application-level error listener is not a complete fix; upgrade to 3.2.6.
“Versions of @fastify/busboy from 1.0.0 through 3.2.5 can be crashed”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · 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 93 if added to CISA KEV
- Would score about 88 if CISA's SSVC rates exploitation active
- Would score about 53 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.
Workaround: Consumers that pass a finite parts limit should attach an 'error' listener to the busboy stream, but this is not a complete fix.
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-124724 (@fastify/busboy vulnerable to Denial of Service via truncated multipart part past the parts limit), 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-124724 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/busboy: from 1.0.0, fixed in 3.2.6
Fixed versions: 3.2.6.
Conditions (all must be true for the bug to be hit):
- Affected versions of @fastify/busboy are 1.0.0 through 3.2.5 (fixed in 3.2.6). (source: https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3)
- The route sets a finite limit on the number of multipart parts (default 1000). (source: https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3)
- The request body can end early, in the middle of a skipped part. (source: https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3)
- The consumer keeps feeding the request body to busboy after a limit error, as @fastify/multipart 10.1.2 through 10.1.4 did. (source: https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Consumers that pass a finite parts limit should attach an 'error' listener to the busboy stream, but this is not a complete fix. (source: https://github.com/fastify/busboy/security/advisories/GHSA-wh8h-qr34-3rj3)
CISA KEV: CVE-2026-124724 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124724 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-wh8h-qr34-3rj3
- 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-124724
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-124724"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
From 1.0.0 · 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.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124724
Is CVE-2026-124724 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 single crafted request can crash the server process. The request body ends in the middle of a skipped multipart part, and busboy emits an 'error' event that nothing handles, so Node exits the process.Source: github.com
Which versions are affected by CVE-2026-124724?
@fastify/busboy (npm): from 1.0.0 before 3.2.6.Source: cve.now feed data
Am I affected, and how do I check?
@fastify/busboy versions 1.0.0 through 3.2.5 are affected, but only on routes that set a finite limit on multipart parts (default 1000). Check the installed version with npm ls @fastify/busboy. The advisory also names @fastify/multipart 10.1.2 through 10.1.4 as an affected setup, because it kept feeding the request body to busboy after a limit error.Source: github.com
How do I fix CVE-2026-124724?
Upgrade @fastify/busboy to 3.2.6, the fixed version. Until you can upgrade, the advisory suggests attaching an 'error' listener to the busboy stream, but it states this is not a complete fix.Source: github.com