Skip to main content
VulnerabilityPublished

CVE-2026-19484: @fastify/busboy vulnerable to Denial of Service via oversized multipart boundary

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 16 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.6% chance of exploitation in 30 days – higher than 50% 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 16 Nov 2026.

What to do

Upgrade @fastify/busboy to 3.2.1.

Affected software

ProductAffectedFixed in
npm@fastify/busboyAffected
  • >=3.1.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, where the vulnerability is fixed. Alternatively, validate the multipart boundary length before parsing and reject any boundary longer than 70 characters (the RFC 2046 limit), for example at a reverse proxy or in an onRequest hook. Upgrading removes the issue entirely.

Description

@fastify/busboy versions from 3.1.0 up to but not including 3.2.1 are vulnerable to a denial of service (DoS) attack. The vulnerability arises from the handling of multipart boundaries in the streaming multipart search, where a crafted boundary of exactly 252 bytes causes a CPU-bound loop that stalls the Node.js event loop. This can be triggered by an unauthenticated client with a single small request. The issue is fixed in version 3.2.1.

References

Community reviews

Loading reviews…