CVE-2026-128846: @fastify/busboy · Off-by-one Error
Affects @fastify/busboySource CVE Database V5
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
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 3.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:NExploitation 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 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.