High [CVE-2026-19484] Denial of Service via oversized multipart boundary
This high-severity Red Hat Linux advisory covers CVE-2026-19484.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
@fastify/busboy is a multipart form-data parser. In versions 3.1.0 through 3.2.0, a remote unauthenticated attacker can stall the Node.js event loop by sending a multipart request whose boundary is crafted to a specific length.
The vendored streaming search stores its skip table in a fixed 256 entry byte array, and a boundary of exactly 252 bytes makes the search needle 256 bytes, which truncates the default skip distance to zero and turns the search into a CPU bound loop on a small body.
A single small request can keep one core busy and deny service to other requests handled by the same process. The issue is fixed in @fastify/busboy 3.2.1, which widens the skip table so the skip distance is preserved.
Users should upgrade to 3.2.1. This can cause the Node.js event loop to stall, leading to a CPU-bound loop that consumes significant processing resources.
Red Hat products that include @fastify/busboy are not affected by this vulnerability. CVE-2026-19484 is present only in @fastify/busboy versions 3.1.0 through 3.2.0.
Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-606.
Red Hat lists OpenShift Pipelines; Red Hat AMQ Broker 7; Red Hat Ceph Storage 8; Red Hat Ceph Storage 9; Red Hat OpenShift AI (RHOAI); Red Hat OpenShift Container Platform 4 as not affected.
- 3.1.0
- 3.2.0
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Mitigation
Upgrade to a fixed release: 3.2.1. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.