Answer in brief
CVE-2026-48862 records a High severity (CVSS 8.2) vulnerability in Unbounded conn.streams growth in Mint HTTP/2 client via unenforced PUSH_PROMISE concurrency. The current sources do not mark it as known exploited. The current feed maps mint (erlang), elixir-mint/elixir-mint/mint (generic), elixir-mint/mint (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mint (erlang), elixir-mint/elixir-mint/mint (generic), elixir-mint/mint (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| minterlang | >=0.2.0,<1.9.0 | 1.9.0 |
| elixir-mint/elixir-mint/mintgeneric | >=65c6394d05a1b8aa4a7461708c3aa173e8d7a5cf <70b97b6a5209fb288b0e04d8e657dda26c59de67 | 70b97b6a5209fb288b0e04d8e657dda26c59de67 |
| elixir-mint/mintgeneric | >=0.2.0 <1.9.0 | 1.9.0 |
Published upstream
Jun 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 10, 2026
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client via PUSH_PROMISE flooding. In lib/mint/http2.ex, Mint.HTTP2.decode_push_promise_headers_and_add_response/5 inserts a :reserved_remote entry into conn.streams for every promised stream ID. The neighbouring Mint.HTTP2.assert_valid_promised_stream_id/2 only verifies that the promised ID is even and not already present; client_settings.max_concurrent_streams is not consulted at promise time. The concurrency cap is only checked when the response HEADERS for the promised stream arrive, so a server that emits PUSH_PROMISE frames and withholds the matching HEADERS never trips that check. HTTP/2 server push is accepted by default (client_settings.enable_push defaults to true). A single long-lived HTTP/2 connection to a hostile server lets that server pin one conn.streams entry per PUSH_PROMISE frame it sends, with no upper bound, until the client process runs out of memory. This issue affects mint: from 0.2.0 before 1.9.0.
Quoted source text, attributed separately from HOL analysis.