CVE-2026-47073

published 25 May 2026 · updated 20 Nov 2026

Unbounded memory consumption in WebSocket client in hackney

9.7CriticalCVSS 8.7EPSS 1%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 4.0.1 and ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc.

Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The WebSocket client in src/hackney_ws.erl imposes no upper bound on memory consumption in three code paths. First, read_handshake_response/3 accumulates received bytes into a growing buffer with no size cap; the per-receive timeout resets on every chunk, so a server that streams bytes without ever sending \r\n\r\n causes the buffer to grow until memory is exhausted. Second, parse_payload/9 and parse_active_payload/8 do not validate the declared frame payload length against any limit; because RFC 6455 allows payload lengths up to 2^63-1 bytes, a server that announces a very large frame and dribbles bytes causes the accumulation buffer to grow until OOM. Third, the frag_buffer field in #ws_data{} accumulates continuation frames indefinitely; a server that sends an endless stream of non-final (nofin) fragmented frames without ever sending a final (fin) frame grows frag_buffer without bound. In all three cases the attacker only needs to control the WebSocket server the hackney client connects to, with no authentication or special client configuration required. This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
benoitc>=2.0.0-beta.1 <4.0.1, >=690cecaf236fba49526da404a5bc889a24367a3e <ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc4.0.1, ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc
benoitchackney>=2.0.0 <4.0.14.0.1

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-47073 severity on Zeptric[![CVE-2026-47073](https://zeptric.io/badge/cve/CVE-2026-47073.svg)](https://zeptric.io/cve/CVE-2026-47073)