What’s Vulnerable › Vulnerabilities

CVE-2026-92103: Mint HTTP/2 client buffers oversized frames up to 16 MiB before enforcing max_frame_size

• Severity: medium (CVSS 6.3 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-28 · updated 2026-09-30
• Weakness: CWE-770

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

• elixir-mint mint: from 0.1.0 before 1.10.2 — fixed in 1.10.2

How to fix

Upgrade to a fixed version: elixir-mint mint 1.10.2. Check the vendor advisory for mitigations.

References

• https://cna.erlef.org/cves/CVE-2026-92103.html
• https://github.com/elixir-mint/mint/commit/20252ca85065f4d1092aed9ee4ed21841a507dfe
• https://github.com/elixir-mint/mint/commit/44d7ce4755d0444ee415cbcca7ce4942382da4dd
• https://github.com/elixir-mint/mint/commit/596ca4304504be68939c4929e0831557097962b8
• https://github.com/elixir-mint/mint/security/advisories/GHSA-q95c-ccq6-j5j6
• https://osv.dev/vulnerability/EEF-CVE-2026-92103

Get alerted when CVE-2026-92103 or the next vulnerability affects your stack