Description
Allocation of Resources Without Limits or Throttling vulnerability in hackney_conn in benoitc hackney allows a malicious HTTP server to exhaust client memory via an oversized or highly compressed response body. hackney:request/5 and hackney:body/1 return the whole response body, and nothing bounds how much the connection process buffers. Any server the client requests can trigger it.
hackney_conn:read_full_body/2 and the HTTP/2 and HTTP/3 accumulators append every chunk until the body ends. With {auto_decompress, true} the buffered body is then inflated in one step with zlib:gunzip/1 or zlib:inflate/2, which return the whole output at once.
This issue affects hackney: from 2.0.0-beta.1 before 4.9.0.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| benoitc | hackney | 2.0.0-beta.1 – < 4.9.0 | 4.9.0 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Hex | hackney | >= 2.0.0-beta.1, < 4.9.0 | 4.9.0 | EEF-CVE-2026-97200 |
References
- hackney 4.9.0 release notes vendor-advisory related
- EEF CNA record for CVE-2026-97200 related
- OSV record EEF-CVE-2026-97200 related
- Cap buffered response bodies with max_body_size and bound decompression (benoitc/hackney#980) related
- Introducing commit dc41b79 in benoitc/hackney related
- Fix commit 493e8bf in benoitc/hackney patch