CVE-2026-92103 json
Mint HTTP/2 client buffers oversized frames up to 16 MiB before enforcing max_frame_size
published last mo. modified last mo. also EEF-CVE-2026-92103 , EUVD-2026-88219 , GHSA-q95c-ccq6-j5j6
- cvss
- 6.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- hex mint 1.10.2
- elixir-mint mint 1.10.2
Is CVE-2026-92103 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | 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 |
| CNA | 4.0 | 6.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | mint | >=0.1.0, <1.10.2 |
1.10.2 |
Affected products
- elixir-mint mint
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/elixir-mint/mint/commit/596ca4304504be68939c4929e0831557097962b8
related, web
-
github.com
/elixir-mint/mint/commit/20252ca85065f4d1092aed9ee4ed21841a507dfe
patch
-
github.com
/elixir-mint/mint/commit/44d7ce4755d0444ee415cbcca7ce4942382da4dd
patch
-
github.com
/elixir-mint/mint/security/advisories/GHSA-q95c-ccq6-j5j6
related, vendor-advisory, advisory
-
cna.erlef.org
/cves/CVE-2026-92103.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-92103
related
-
hex.pm
/packages/mint
package
Sources
- CVE List CVE-2026-92103
- NVD CVE-2026-92103
- OSV EEF-CVE-2026-92103
- Maintainer advisory GHSA-q95c-ccq6-j5j6
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of elixir-mint/mint published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.