CVE-2026-82728
Allocation of Resources Without Limits or Throttling vulnerability …
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a remote HTTP server to exhaust memory on the client host and cause a denial of service. Two HTTP/1 response-parser states accumulate server data without any cap. In lib/mint/http1.ex, decode_status_line/4 stores the unconsumed data in conn.buffer when the status line is incomplete, and decode_body/5 does the same for an unterminated chunk-extension line. Both wait for a CRLF the server never has to send, and conn.buffer is prepended to every subsequent socket message. The :max_header_list_size budget is wired only into decode_headers/5 and decode_trailer_headers/4, so neither of these states is covered by it. A malicious server, or one reached through an attacker-controlled redirect or a fetched URL, streams bytes indefinitely until the BEAM node is killed by the operating system out-of-memory handler. The chunk-extension variant is reached after a valid status line and a complete, valid header section, so an intermediary inspecting only headers sees an ordinary 200 response. This issue affects mint: from 0.1.0 before 1.10.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- cna.erlef.org/cves/CVE-2026-82728.html
- github.com/elixir-mint/mint/commit/19be5558b6a317e271c78666498dd78b151e490a
- github.com/elixir-mint/mint/security/advisories/GHSA-g83f-2j6r-q6m4
- osv.dev/vulnerability/EEF-CVE-2026-82728
- github.com/elixir-mint/mint/commit/c088e4b6430545338841ab8d294369e45d39856a
- nvd.nist.gov/vuln/detail/CVE-2026-82728
- cve.org/CVERecord?id=CVE-2026-82728
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.