Skip to main content
VulnerabilityPublished Updated

CVE-2026-124724: Node undici · @fastify/busboy is a streaming parser for multipart form data used by Fastify

Affects node-undiciSource GCVE Database

0
Compare
Authoritative record:CVE-2026-124724· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 3.2.6 : patch node-undici soon.

Data as of 18 Nov 2026, 16:33 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.17.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 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

Affected software

ProductAffectedFixed in
Ubuntu 26.10node-undicipkg:deb/ubuntu/node-undici?arch=source&distro=stonkingOther threatsAffected
  • 7.18.2+dfsg+~cs3.2.0-1build1 – 8.9.0+dfsg+~cs3.2.0-1
5 affected builds
Fixed in–
Ubuntu 26.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=resoluteOther threatsAffected
  • 7.3.0+dfsg1+~cs24.12.11-2 – 7.18.2+dfsg+~cs3.2.0-1build1
4 affected builds
Fixed in–
Ubuntu 24.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=nobleOther threatsAffected
  • =5.22.1+dfsg1+~cs20.10.10.2-1ubuntu1
  • =5.26.3+dfsg1+~cs23.10.12-2
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 runs. 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 exceeding the configured multipart parts limit causes skipped parts without error listeners. If the request body ends prematurely in such a skipped part, an unhandled error event causes the Node.js process to crash. This allows an unauthenticated attacker to cause a denial of service by sending a crafted request. The issue is fixed in version 3.2.6.

References

Community reviews

Loading reviews…