CVE-2026-92103
Mint HTTP/2 client buffers oversized frames up to 16 MiB before enforcing max_frame_size
- State
- Published
- Severity
- 6.3 Medium
- Published
- Sep 28, 2026
- Updated
- Sep 30, 2026
- Reserved
- Sep 15, 2026
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 6.3 Medium | 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 | EEF |
Weaknesses
- CWE-770 Allocation of Resources Without Limits or Throttling
Affected Products
| Product | Versions |
|---|---|
mintelixir-mint |
|
mintelixir-mint |
|
References
- GitHub Advisoryrelatedvendor-advisory
- EEF CNA record for CVE-2026-92103related
- OSV record EEF-CVE-2026-92103related
- Introducing commit 596ca43 in elixir-mint/mintrelated
- Fix commit 20252ca in elixir-mint/mintpatch
- Fix commit 44d7ce4 in elixir-mint/mintpatch
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.