Skip to main content
Menu
CVEs

CVE

Fastify Busboy multipart parser flaw lets uploads skip file checks

CVE-2026-128846EUVD-2026-126379

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

3.7LowCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.6
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.2.6.

Published
Last modified
Reference
Last checked
41/100 · provisional
35% of @fastify/busboy downloads last week were affected versions (18.1M).npm, 51.4M downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The @fastify/busboy multipart form parser, used by Fastify, can be made to treat a binary file upload as a plain text field when the header data is split at a specific point across network reads. A remote client can trigger this without logging in, and an application that checks only file uploads, such as with malware scanning, may process the payload without those checks.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 3.2.1 through 3.2.5, the parser can interpret the same multipart bytes differently depending on how they are split across socket reads: when the sequence that terminates a part's header block arrives split exactly at the configured header size limit, an off by one error drops the final header line, so a part declared as a binary file attachment is emitted as an ordinary text field instead of a file. A remote client controls both the multipart body and the header padding needed to reach the boundary and can influence segmentation, so an application that applies upload validation such as malware scanning or extension checks only to file events while trusting plain field values may process the payload through the wrong path. The parser level type confusion is fully reproducible, while the downstream validation bypass depends on the application. The issue is fixed in @fastify/busboy 3.2.6, which tracks how many terminator bytes were actually buffered when the limit is reached so a split terminator no longer corrupts the final header, and users should upgrade to 3.2.6 or later. As a workaround, apply the same validation to field values as to file uploads rather than treating file events as a trust boundary.

cve.now Index

41Pcve.now Index 41 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach20/20@fastify/busboy: 51.4M downloads a week
  • Severity3.7/10CVSS 3.7
  • No patch0/5No signal

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active
  • Would score about 46 if advisories confirm default setups are exposed

Impact

  • Widely used

    @fastify/busboy has 51.4m weekly downloads.Source: npmjs.com

What to do

  • Upgrade to a fixed version: 3.2.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128846 (@fastify/busboy vulnerable to multipart file/field type confusion via chunk-dependent header parsing), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128846 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/busboy: from 3.2.1, fixed in 3.2.6
Fixed versions: 3.2.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128846 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128846 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/busboy/security/advisories/GHSA-2q57-jvxc-h47j
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128846
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128846"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • From 3.2.1 · fixed in 3.2.6

    Fixed in 3.2.6 (released Nov 16, 2026, the day of disclosure).

    The latest release, 3.2.6, is not affected.

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128846

Is CVE-2026-128846 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-128846?

@fastify/busboy (npm): from 3.2.1 before 3.2.6.Source: cve.now feed data

How do I fix CVE-2026-128846?

Upgrade to a fixed version: 3.2.6.Source: cve.now feed data