# CVE-2026-92103: Elixir Mint HTTP/2 frame buffer exhaustion

Source: https://junglewise.ai/threats/cve-2026-92103-allocation-of-resources-without-limits-or-throttling  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-28. Updated: 2026-09-28  
License: CC BY 4.0 with a link back

CVE-2026-92103 · Severity: info · Published 2026-09-28

Mint is an HTTP client library for Elixir used in applications that make HTTP requests. A malicious HTTP/2 server can cause the Mint client to accumulate approximately 16 MB of data in memory by declaring oversized frames and withholding the final bytes, leading to uncontrolled memory consumption and potential denial of service.

Technologies: [Elixir-Mint Mint](https://junglewise.ai/threats/technologies/mint). Vendors: [Elixir-Mint](https://junglewise.ai/threats/vendors/elixir-mint).

## Quick answers

**Is CVE-2026-92103 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92103 being exploited in the wild.

**How severe is CVE-2026-92103?** Informational severity, published 28 September 2026.

**Which products and versions are affected?** Elixir-Mint Mint 0.1.0 before 1.11.0.

**Is there a fix for CVE-2026-92103?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92103 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-92103?** Check whether you run Elixir-Mint Mint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in Mint.HTTP2.Frame.decode_next/2, which validates frame size only after the complete declared payload arrives. An attacker can send frames declaring lengths up to 16,777,215 bytes (the 24-bit limit) and delay the final byte, causing the client to buffer approximately 1,024 times the default max frame size (16 KB) per connection. This is a resource exhaustion issue requiring network proximity and an active HTTP/2 connection, with no amplification as the server must send all buffered bytes.

## Affected products

- elixir-mint Mint 0.1.0 before 1.11.0

## Timeline

- 2026-09-28: disclosed

## References

- [https://repo.hex.pm/](https://repo.hex.pm/)
- [https://github.com/](https://github.com/)

## Related threats

- [Mint HTTP request/response smuggling in transfer encoding parsing](https://junglewise.ai/threats/cve-2026-94194-inconsistent-interpretation-of-http-requests-http-request)
- [Mint HTTP/2 header list memory exhaustion denial of service](https://junglewise.ai/threats/cve-2026-91043-allocation-of-resources-without-limits-or-throttling)
- [Elixir Mint HTTP request smuggling in chunked transfer encoding](https://junglewise.ai/threats/cve-2026-82672-inconsistent-interpretation-of-http-requests-http-request)
- [elixir-mint HTTP/1 parser algorithmic complexity denial of service](https://junglewise.ai/threats/cve-2026-82729-elixir-mint-http-1-parser-algorithmic-complexity-denial-of)
- [Elixir Mint HTTP/1 parser denial of service via unbounded buffer](https://junglewise.ai/threats/cve-2026-82728-elixir-mint-http-1-parser-denial-of-service-via-unbounded-buffer)