CVE-2026-58229

Unbounded HTTP/1 response-header and chunked-trailer accumulation in Mint causes memory-exhaustion DoS

HIGH
8.2
CVSS Score
Published: July 14, 2026 at 08:36 AM UTC
Updated: July 15, 2026 at 08:30 PM UTC
1 product affected across 1 vendorMint

Using mint by elixir-mint?

Get instant alerts when new vulnerabilities affect mint - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.5%
SSVC
PoC

Description

Allocation of resources without limits vulnerability in elixir-mint mint allows a remote HTTP server to exhaust memory on the client host and cause a denial of service. The Mint.HTTP1.decode_headers/5 and Mint.HTTP1.decode_trailer_headers/4 functions in lib/mint/http1.ex accumulate every parsed response header and chunked-trailer field into a per-request list that persists across incoming TCP segments as request.headers_buffer, and only clear it when the terminating blank line is received. The section has no cap on the number of headers or on total bytes, and the underlying :erlang.decode_packet(:httph_bin, binary, []) parser is invoked with an empty option list so its per-line and per-packet size limits also default to unlimited. A malicious HTTP server (reachable directly, via an attacker-controlled redirect, via SSRF, or via a man-in-the-middle) can stream complete header lines (or, after a chunked body, complete trailer lines) indefinitely without ever emitting the terminating blank line. The connection state grows without bound until the BEAM node is killed by the operating system's out-of-memory handler, taking down the entire application that uses Mint as an HTTP client. This issue affects mint: from 0.1.0 before 1.9.2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.1.0 ≤ v < 1.9.20.1.03e6de4bac4821b0eb4d6109e8b1f3fb6458792c8
Vendor states this is fixed in 566d702e6f29105f77522ca7aabb9f64f2f4e333 (fixed)
Affected range stops below 1.9.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

Related
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://cna.erlef.org/cves/CVE-2026-58229.html
Vendor AdvisoryRelated
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://github.com/elixir-mint/mint/security/advisories/GHSA-qrfr-wh4c-3qhw
Related
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://osv.dev/vulnerability/EEF-CVE-2026-58229

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card