CVE-2026-56810: CWE-770 Allocation of Resources Without Limits or Throttling in elixir-mint mint
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.
AI Analysis
Technical Summary
The vulnerability arises because Mint.HTTP1 accumulates partial fragments of chunked HTTP response bodies in an unbounded buffer until the entire declared chunk is received. The chunk size is parsed directly from the server response without an upper bound. An attacker-controlled server can announce a very large chunk size (e.g., ~2 GiB) and send data slowly without completing the chunk, causing the client to buffer all received bytes indefinitely. This behavior can lead to excessive memory consumption and out-of-memory conditions, resulting in denial of service. The affected code is in lib/mint/http1.ex, specifically the decode_body/5 and add_body_to_buffer/2 routines. The vulnerability affects mint versions =0.5.0 and >=0.5.0 <1.9.1.
Potential Impact
An unauthenticated remote server can exploit this vulnerability by sending a malicious chunked HTTP response with an oversized chunk size and slow data transmission. This causes the client to buffer data indefinitely, potentially exhausting system memory and causing a denial of service. The impact is high due to the ability to crash or severely degrade client applications that use the affected mint versions when processing untrusted HTTP responses.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, 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. Monitor vendor channels for updates and apply official patches once released.
CVE-2026-56810: CWE-770 Allocation of Resources Without Limits or Throttling in elixir-mint mint
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.
CVSS v4.0
Score 8.7high
Affected software
cpe:2.3:a:elixir-mint:mint:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because Mint.HTTP1 accumulates partial fragments of chunked HTTP response bodies in an unbounded buffer until the entire declared chunk is received. The chunk size is parsed directly from the server response without an upper bound. An attacker-controlled server can announce a very large chunk size (e.g., ~2 GiB) and send data slowly without completing the chunk, causing the client to buffer all received bytes indefinitely. This behavior can lead to excessive memory consumption and out-of-memory conditions, resulting in denial of service. The affected code is in lib/mint/http1.ex, specifically the decode_body/5 and add_body_to_buffer/2 routines. The vulnerability affects mint versions =0.5.0 and >=0.5.0 <1.9.1.
Potential Impact
An unauthenticated remote server can exploit this vulnerability by sending a malicious chunked HTTP response with an oversized chunk size and slow data transmission. This causes the client to buffer data indefinitely, potentially exhausting system memory and causing a denial of service. The impact is high due to the ability to crash or severely degrade client applications that use the affected mint versions when processing untrusted HTTP responses.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, 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. Monitor vendor channels for updates and apply official patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-06-23T12:29:02.507Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b81c327e9c797194eed38
Added to database: 07/06/2026, 10:21:55 UTC
Last enriched: 07/06/2026, 10:36:44 UTC
Last updated: 08/19/2026, 23:20:00 UTC
Views: 108
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.