Skip to main content
VulnerabilityPublished

CVE-2026-128846: @fastify/busboy · Off-by-one Error

Affects @fastify/busboySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 3.2.6 when convenient.

Data as of 16 Nov 2026, 13:51 UTC

CVSS 3.1 base score
3.7Low
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.13.7
Patch
Available – fixed in 3.2.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

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 15 Nov 2026.

What to do

Upgrade @fastify/busboy to 3.2.6.

Affected software

ProductAffectedFixed in
@fastify/busboy@fastify/busboyAffected
  • >=3.2.1 <3.2.6
Fixed in
  • 3.2.6
npm@fastify/busboypkg:npm/@fastify/busboyOther threatsAffected
  • >=3.2.1 <3.2.6
Fixed in
  • 3.2.6

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 the issue is fixed. As a workaround, apply the same validation rules to all multipart form fields, not just file uploads, to avoid trusting plain field values as a security boundary.

Description

@fastify/busboy versions 3.2.1 through 3.2.5 contain an off-by-one error in the multipart form data parser. This flaw causes the parser to misinterpret multipart bytes when the terminating sequence of a part's header block is split exactly at the configured header size limit. As a result, a file attachment part may be incorrectly emitted as a plain text field. This can lead to validation bypass if the application applies stricter checks only to file uploads and trusts plain fields. The issue is fixed in version 3.2.6.

References

Community reviews

Loading reviews…