Description
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a remote HTTP server to exhaust memory on the client host and cause a denial of service.

Two HTTP/1 response-parser states accumulate server data without any cap. In lib/mint/http1.ex, decode_status_line/4 stores the unconsumed data in conn.buffer when the status line is incomplete, and decode_body/5 does the same for an unterminated chunk-extension line. Both wait for a CRLF the server never has to send, and conn.buffer is prepended to every subsequent socket message. The :max_header_list_size budget is wired only into decode_headers/5 and decode_trailer_headers/4, so neither of these states is covered by it. A malicious server, or one reached through an attacker-controlled redirect or a fetched URL, streams bytes indefinitely until the BEAM node is killed by the operating system out-of-memory handler. The chunk-extension variant is reached after a valid status line and a complete, valid header section, so an intermediary inspecting only headers sees an ordinary 200 response.

This issue affects mint: from 0.1.0 before 1.10.0.
Published: 2026-09-04
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Unbounded buffering of HTTP/1 status lines and chunk-extensions in the Mint client causes the application to allocate memory without limits, resulting in a denial of service when a malicious HTTP server sends large or incomplete lines that the client never terminates. This lack of throttling demonstrates Resource Exhaustion (CWE-770) and can quickly consume all memory on the BEAM node, leading the operating system to terminate the process. The vulnerability is exploitable when a client connects to an attacker‑controlled or redirected endpoint capable of streaming arbitrary data.

Affected Systems

The Mint library for Elixir, versions from 0.1.0 up to, but not including, 1.10.0, is affected. Any application that relies on Mint for HTTP/1 communication is susceptible because the flaw exists in both status-line parsing and chunk-extension handling and is not mitigated by the :max_header_list_size setting.

Risk and Exploitability

The CVSS base score of 8.2 classifies the flaw as High severity; the EPSS score is not available, yet the attack vector is remote, requiring only a crafted HTTP response from an untrusted server. Although not listed in the CISA KEV catalog, the design permits passive exploitation over any HTTP/S connection, making it a realistic risk for affected deployments. Immediate patching or mitigation is strongly advised.

Generated by OpenCVE AI on September 4, 2026 at 15:30 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Mint library to version 1.10.0 or newer.
  • If an upgrade cannot be performed immediately, configure your HTTP client or use a proxy to enforce limits on status lines and chunk-extensions before they are passed to the client.
  • Monitor the application’s memory usage and implement process limits or restart policies to mitigate the impact of an out‑of‑memory event.

Generated by OpenCVE AI on September 4, 2026 at 15:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
Description Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a remote HTTP server to exhaust memory on the client host and cause a denial of service. Two HTTP/1 response-parser states accumulate server data without any cap. In lib/mint/http1.ex, decode_status_line/4 stores the unconsumed data in conn.buffer when the status line is incomplete, and decode_body/5 does the same for an unterminated chunk-extension line. Both wait for a CRLF the server never has to send, and conn.buffer is prepended to every subsequent socket message. The :max_header_list_size budget is wired only into decode_headers/5 and decode_trailer_headers/4, so neither of these states is covered by it. A malicious server, or one reached through an attacker-controlled redirect or a fetched URL, streams bytes indefinitely until the BEAM node is killed by the operating system out-of-memory handler. The chunk-extension variant is reached after a valid status line and a complete, valid header section, so an intermediary inspecting only headers sees an ordinary 200 response. This issue affects mint: from 0.1.0 before 1.10.0.
Title Unbounded HTTP/1 status-line and chunk-extension buffering in Mint causes memory-exhaustion DoS
First Time appeared Elixir-mint
Elixir-mint mint
Weaknesses CWE-770
CPEs cpe:2.3:a:elixir-mint:mint:*:*:*:*:*:*:*:*
Vendors & Products Elixir-mint
Elixir-mint mint
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'}


Subscriptions

Elixir-mint Mint
cve-icon MITRE

Status: PUBLISHED

Assigner: EEF

Published:

Updated: 2026-09-04T19:32:44.727Z

Reserved: 2026-08-31T00:59:08.960Z

Link: CVE-2026-82728

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T15:17:35.943

Modified: 2026-09-04T20:17:29.797

Link: CVE-2026-82728

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T15:30:07Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling