CVE-2026-128842: Node undici · @fastify/busboy is a streaming parser for multipart and url-encoded form data used by
Affects node-undiciSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 3.2.6 : update node-undici when convenient.
Data as of 18 Nov 2026, 16:05 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 5.3 |
|---|
- 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:LExploitation 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10node-undicipkg:deb/ubuntu/node-undici?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=nobleOther 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 by enforcing the per-field size limit correctly. As a workaround, configure a conservative whole-request body size limit to prevent a single field from growing beyond acceptable memory usage. No other actions are specifically recommended.
Description
@fastify/busboy versions 1.0.0 through 3.2.5 contain a vulnerability in the url-encoded form data parser where a malformed percent escape can cause the decoded field length to bypass the configured per-field size limit. This allows a single unauthenticated field to grow in memory up to the size of the entire request body, potentially leading to excessive memory consumption. The issue is fixed in version 3.2.6.