CVE-2026-56810: mint · Unthrottled Resource Allocation
Affects mintSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.9.1 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.1, 193ce714907d16e8adc4ab3c40e4f0c2f045b2a6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade mint to 1.9.1; mint to 193ce714907d16e8adc4ab3c40e4f0c2f045b2a6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| elixir-mintmint | Affected
| Fixed in
|
| elixir-mintmint | Affected
| Fixed in
|
Hexmintpkg:hex/mintOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:elixir-mint:mint:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid processing untrusted HTTP responses with mint versions =0.5.0 and >=0.5.0 <1.9.1, or implement external safeguards such as limiting memory usage or restricting redirects and user-supplied URLs.
Description
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint (Mint.HTTP1 module) allows a denial of service via an oversized chunked transfer-encoded response. This vulnerability is associated with program files lib/mint/http1.ex and program routines 'Elixir.Mint.HTTP1':decode_body/5, 'Elixir.Mint.HTTP1':add_body_to_buffer/2. When Mint decodes a chunked HTTP response body, it accumulates each partial fragment of the current chunk in the connection's data_buffer (an unbounded iolist) via add_body_to_buffer/2 and does not emit the data to the caller until the full declared chunk length has been received. The chunk size is taken directly from the server and parsed with no upper bound, so a malicious or compromised server can announce one enormous chunk (for example a size line of 7FFFFFFF, about 2 GiB) and then send the body bytes slowly without ever completing the chunk. The client buffers every received byte while it waits for a completion that never arrives, and because no data responses are produced until the chunk finishes, a caller that otherwise streams large content-length bodies safely gains no protection. An unauthenticated remote server (reachable whenever a client follows redirects, fetches user-supplied URLs, or processes webhooks) can drive the client's memory arbitrarily high and trigger an out-of-memory condition. This issue affects mint: from 0.5.0 before 1.9.1.
References
- github.com/elixir-mint/mint/security/advisories/GHSA-c59h-fq4p-r36r (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-56810.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-56810 (opens in a new tab)
- github.com/elixir-mint/mint/commit/193ce714907d16e8adc4ab3c40e4f0c2f045b2a6 (opens in a new tab)