Skip to main content
Menu
CVEs

CVE

Fastify Busboy denial of service in URL-encoded form parsing

CVE-2026-128842EUVD-2026-126377

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

5.3MediumCNA
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
42/100 · provisional
100% of @fastify/busboy downloads last week were affected versions (51.4M).npm, 51.4M downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub

Summary

The @fastify/busboy package can be made to use excessive memory, causing a denial of service. An attacker can trigger this remotely, without logging in, by sending a single URL-encoded form field or field name that grows to the size of the whole request body, bypassing the configured per-field size limit.

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

Original description

@fastify/busboy is a streaming parser for multipart and url-encoded form data used by Fastify. In versions 1.0.0 through 3.2.5, the url-encoded parser stops accumulating a field only when the decoded length exactly equals the configured per-field size limit, and a malformed percent escape is passed through verbatim by the decoder, so the decoded length can jump from just below the limit to just above it and skip that equality check. The parser then keeps buffering the field in memory until the next delimiter or the end of the request, so a single unauthenticated url-encoded field or field name can grow to the size of the whole request body regardless of a much smaller configured per-field limit, with memory use bounded only by the independent whole-request body limit. The issue is fixed in @fastify/busboy 3.2.6, which clamps a field as soon as the decoded length reaches or exceeds the limit, and users should upgrade to 3.2.6 or later. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.

cve.now Index

42Pcve.now Index 42 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • 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
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 87 if added to CISA KEV
  • Would score about 82 if CISA's SSVC rates exploitation active
  • Would score about 47 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-128842 (@fastify/busboy vulnerable to Denial of Service via URL-encoded field size-limit bypass), 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-128842 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/busboy: 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-128842 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128842 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-x578-65c5-rvww
- 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-128842
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-128842"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • 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-128842

Is CVE-2026-128842 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-128842?

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

How do I fix CVE-2026-128842?

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