CVE-2026-49754
Allocation of Resources Without Limits or Throttling vulnerability …
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood). When Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity). A malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient. This issue affects mint: from 0.1.0 before 1.9.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-49754.html
- github.com/elixir-mint/mint/commit/b662d127d3028b5426c88d4c9cc7fe430491a10b
- github.com/elixir-mint/mint/security/advisories/GHSA-2p26-p43x-fhp8
- osv.dev/vulnerability/EEF-CVE-2026-49754
- nvd.nist.gov/vuln/detail/CVE-2026-49754
- github.com/advisories/GHSA-2p26-p43x-fhp8
- github.com/elixir-mint/mint/commit/596ca4304504be68939c4929e0831557097962b8
- nvd.nist.gov/vuln/detail/CVE-2026-49754
- cve.org/CVERecord?id=CVE-2026-49754
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.