Description
Allocation of resources without limits vulnerability in elixir-mint mint allows a remote HTTP/2 server to exhaust memory on the client host and cause a denial of service.

The Mint.HTTP2.handle_continuation/3 function in lib/mint/http2.ex accumulates the header-block fragment carried by each HTTP/2 CONTINUATION frame into a growing conn.headers_being_processed nesting, one level deeper per frame, and only releases it when a frame with the END_HEADERS flag arrives. The only guard on this accumulator is Mint.HTTP2.assert_header_block_within_max_size/2, which sums the byte size of the fragments received so far. Because a CONTINUATION frame is permitted by the protocol to carry a zero-length payload, an unbounded chain of zero-length CONTINUATION frames adds no bytes to the running total, never trips the size cap, and never emits END_HEADERS, yet each frame still nests the accumulator one level deeper.

A malicious HTTP/2 server (reachable directly, via an attacker-controlled redirect, via SSRF, or via a man-in-the-middle) can open a stream by sending a HEADERS frame without END_HEADERS and then stream zero-length CONTINUATION frames indefinitely. Client memory grows one cons cell per frame received; sustained bandwidth from the peer drives the BEAM node running the Mint client to memory exhaustion and eventual out-of-memory termination.

This issue affects mint: from 0.1.0 before 1.9.2.
Published: 2026-07-14
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a resource‑exhaustion flaw in the Mint HTTP/2 client library. The client accumulates header‑block fragments when processing a series of CONTINUATION frames. Because an attacker can send an endless chain of zero‑length CONTINUATION frames without triggering the size limit. Each frame increases a nested data structure, so client memory grows unbounded, eventually exhausting.

Affected Systems

The flaw affects the Elixir Mint HTTP client, specifically the mint project ( from 0.1.0 up to but not including 1.9.2 are vulnerable. Clients that use the library in HTTP/2 contexts are at risk. No specific OS or platform is singled out, as the issue lies in the library code.

Risk and Exploitability

The CVSS base score of 6.3 indicates a moderate severity, and the EPSS score under 1% implies that exploitation is currently considered unlikely. The flaw is not listed in CISA's KEV catalog. The attacker requires the ability to act as an HTTP/2 server reachable from the client – which can be achieved directly, via redirect, SSRF, or MITM. Once connected, the attacker can send a HEADERS frame followed by an unlimited stream of zero‑length CONTINUATION frames, forcing the client to allocate memory until the BEAM node terminates. Because the issue is triggered by data from an external party, the attack vector is remote and does not depend on local code execution.

Generated by OpenCVE AI on July 31, 2026 at 10:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Mint to version 1.9.2 or later, where the vulnerability has been addressed by bounding the header‑block accumulator.
  • If an upgrade is not possible, disable HTTP/2 support in the application or restrict the library to trusted servers to limit exposure.
  • Implement application‑level memory monitoring and restart or gracefully terminate the BEAM process defined threshold, to contain the impact if an attacker manages to trigger the flaw.

Generated by OpenCVE AI on July 31, 2026 at 10:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 14 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 14 Jul 2026 09:15:00 +0000

Type Values Removed Values Added
Description Allocation of resources without limits vulnerability in elixir-mint mint allows a remote HTTP/2 server to exhaust memory on the client host and cause a denial of service. The Mint.HTTP2.handle_continuation/3 function in lib/mint/http2.ex accumulates the header-block fragment carried by each HTTP/2 CONTINUATION frame into a growing conn.headers_being_processed nesting, one level deeper per frame, and only releases it when a frame with the END_HEADERS flag arrives. The only guard on this accumulator is Mint.HTTP2.assert_header_block_within_max_size/2, which sums the byte size of the fragments received so far. Because a CONTINUATION frame is permitted by the protocol to carry a zero-length payload, an unbounded chain of zero-length CONTINUATION frames adds no bytes to the running total, never trips the size cap, and never emits END_HEADERS, yet each frame still nests the accumulator one level deeper. A malicious HTTP/2 server (reachable directly, via an attacker-controlled redirect, via SSRF, or via a man-in-the-middle) can open a stream by sending a HEADERS frame without END_HEADERS and then stream zero-length CONTINUATION frames indefinitely. Client memory grows one cons cell per frame received; sustained bandwidth from the peer drives the BEAM node running the Mint client to memory exhaustion and eventual out-of-memory termination. This issue affects mint: from 0.1.0 before 1.9.2.
Title Zero-length HTTP/2 CONTINUATION frames bypass Mint's header-block byte-size cap and exhaust client memory
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': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

Elixir-mint Mint
cve-icon MITRE

Status: PUBLISHED

Assigner: EEF

Published:

Updated: 2026-07-14T15:08:39.463Z

Reserved: 2026-07-04T04:24:03.652Z

Link: CVE-2026-59246

cve-icon Vulnrichment

Updated: 2026-07-14T12:24:16.265Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T10:45:04Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling