Quick answers
- Is CVE-2026-56810 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56810 being exploited in the wild.
- How severe is CVE-2026-56810?
- Informational severity, with a CVSS score of 8.7, published 6 July 2026.
- Which products and versions are affected?
- Elixir-Mint Mint 0.5.0 to 1.9.0.
- Is there a fix for CVE-2026-56810?
- A patch was published on 2026-07-06. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56810 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56810?
- Check whether you run Elixir-Mint Mint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A resource exhaustion vulnerability exists in the Mint.HTTP1 module of the Elixir Mint library. The root cause is located in the 'decode_body/5' and 'add_body_to_buffer/2' routines, where the decoder parses chunk sizes from a server without an upper bound and buffers all partial fragments in an unbounded iolist until the full declared chunk length is received. An unauthenticated remote attacker can exploit this by serving a response with a massive chunk size (e.g., 2 GiB) and never completing the chunk, bypassing streaming protections and driving the client's memory usage until an out-of-memory (OOM) condition occurs. This affects versions 0.5.0 through 1.9.0 and is fixed in version 1.9.1.
Affected products
- elixir-mint mint 0.5.0 to 1.9.0
Timeline
- 2026-07-06: advisory
- 2026-07-06: disclosed
- 2026-07-06: patched