Skip to main content
VulnerabilityPublished

CVE-2026-19481: @fastify/busboy vulnerable to Denial of Service via prototype-named multipart part header

Affects @fastify/busboySource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.2.1 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade @fastify/busboy to 3.2.1.

Affected software

ProductAffectedFixed in
npm@fastify/busboyAffected
  • >=1.0.0 <3.2.1
Fixed in
  • 3.2.1

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.1 or later to fully resolve the issue. As a workaround, attach an 'error' event listener to the Busboy stream to handle parser failures gracefully and wrap direct write()/end() calls in try/catch blocks to prevent process termination. However, upgrading is the recommended and complete fix.

Description

@fastify/busboy versions from 1.0.0 up to but not including 3.2.1 are vulnerable to a denial of service (DoS) caused by multipart header names that collide with JavaScript prototype properties. This leads to a TypeError and can crash the Node.js process if unhandled. The vulnerability affects any unauthenticated client able to submit multipart/form-data requests. The issue is fixed in version 3.2.1.

References

Community reviews

Loading reviews…