Vulnerability · Published Sep 28, 2026 · Assigned by EEF
CVE-2026-92103Mint HTTP/2 client buffers oversized frames up to 16 MiB before enforcing max_frame_size
Medium 6.3
In plain English
A medium-severity resource allocation without limits in mint from elixir-mint. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 26% of all known vulnerabilities).
Official description
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a malicious HTTP/2 server to make the client hold up to about 16 MiB per connection in frames it should reject, consuming client memory. Mint.HTTP2.Frame.decode_next/2 in lib/mint/http2/frame.ex compares a frame with the client's max_frame_size (16,384 bytes by default) only once the whole declared payload has arrived. Until then it returns :more, and Mint.HTTP2 keeps every received byte in the connection buffer. A server can declare a frame length of up to 16,777,215 bytes and withhold the last byte, keeping roughly 1,024 times the advertised limit buffered for as long as the connection stays open. The server has to send every byte the client buffers, so there is no amplification, and the buffer stops at the 24-bit frame length limit. This issue affects mint: from 0.1.0 before 1.10.2.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| elixir-mint | mint | 0.1.0 – before 1.10.2 |
| elixir-mint | mint | 596ca4304504be68939c4929e0831557097962b8 – before * |
Weakness: CWE-770 · Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
References
- GitHub Advisory related, vendor-advisory
- EEF CNA record for CVE-2026-92103 related
- OSV record EEF-CVE-2026-92103 related
- Introducing commit 596ca43 in elixir-mint/mint related
- Fix commit 20252ca in elixir-mint/mint patch
- Fix commit 44d7ce4 in elixir-mint/mint patch