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.
Published: 2026-10-26
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: Memory Exhaustion leading to Denial of Service
Action: Patch Immediately
AI Analysis

Impact

A lack of bounding on response body buffering in hackney allows a malicious HTTP server to send an oversized or highly compressed response. When the client receives such a response, it stores the entire body in memory before decompressing it with zlib. The combination of an unbounded buffer and a single‑pass decompression can consume an attacker‑designated amount of client memory, potentially crashing the client or causing a denial of service. The flaw is a classic example of CWE‑409 (Race Condition) and CWE‑770 (Out‑of‑Bounds Buffer Access).

Affected Systems

The vulnerability affects the Elixir/Erlang HTTP client library hackney for vendors benoitc, covering versions from 2.0.0‑beta.1 up through, but not including, 4.9.0. The specific package is all of hackney’s HTTP request handling functions that read full bodies or stream content.

Risk and Exploitability

The CVSS score of 8.2 classifies this as a high‑severity flaw, and the absence of an EPSS score leaves the exact exploitation likelihood unknown, but the flaw is straightforward to trigger: an attacker simply acts as an HTTP server and sends a large or compressed response to any client using the vulnerable library. The vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread known exploitation, yet the attack vector is trivial for an attacker controlling a target endpoint. The recommended mitigation is to upgrade to a version that limits buffered data or otherwise applies throttling.

Generated by OpenCVE AI on October 26, 2026 at 15:36 UTC.

Remediation

Vendor Workaround

Leave auto_decompress disabled (the default). Without it hackney_conn:maybe_decompress_body/2 never inflates the body, which closes the amplification half. The uncapped raw body read has no workaround.


OpenCVE Recommended Actions

  • Upgrade hackney to 4.9.0 or newer
  • Disable auto_decompress when communicating with untrusted servers (the default is safe)
  • Implement a maximum response body size limit or stream the response incrementally to prevent large payload consumption

Generated by OpenCVE AI on October 26, 2026 at 15:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 26 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 26 Oct 2026 14:00:00 +0000

Type Values Removed Values Added
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.
Title Unbounded response body buffering and decompression in hackney
First Time appeared Benoitc
Benoitc hackney
Weaknesses CWE-409
CWE-770
CPEs cpe:2.3:a:benoitc:hackney:*:*:*:*:*:*:*:*
Vendors & Products Benoitc
Benoitc hackney
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: EEF

Published:

Updated: 2026-10-26T15:35:50.487Z

Reserved: 2026-10-26T05:15:01.465Z

Link: CVE-2026-97200

cve-icon Vulnrichment

Updated: 2026-10-26T15:32:12.835Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-26T14:16:42.180

Modified: 2026-10-26T16:59:16.113

Link: CVE-2026-97200

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-26T17:00:15Z

Weaknesses
  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

  • CWE-770

    Allocation of Resources Without Limits or Throttling