CVE-2026-124724: @fastify/busboy · Uncaught Exception
Affects @fastify/busboySource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.2.6 soon.
Data as of 16 Nov 2026, 13:50 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 3.2.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade @fastify/busboy to 3.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/busboy@fastify/busboy | Affected
| Fixed in
|
npm@fastify/busboypkg:npm/@fastify/busboyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @fastify/busboy to version 3.2.6 or later, where this issue is fixed. There is no complete application-level workaround because the crash occurs inside the parser before application code executes. Consumers that set a finite parts limit should also attach an error listener to the parser stream to handle errors gracefully.
Description
@fastify/busboy versions 1.0.0 through 3.2.5 contain a vulnerability where an uncaught exception in the multipart form data parser can cause the Node.js process to crash. This occurs when the number of multipart parts exceeds a configured limit, leading to skipped parts without error listeners. If the request body ends prematurely during a skipped part, an error event is emitted without a listener, causing an unhandled exception and server crash. The issue is fixed in version 3.2.6.