Quick answers
- Is CVE-2026-48862 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48862 being exploited in the wild.
- How severe is CVE-2026-48862?
- High severity, with a CVSS score of 8.2, published 2 June 2026.
- Which products and versions are affected?
- Elixir-Mint Mint >= 0.2.0, < 1.9.0.
- Is there a fix for CVE-2026-48862?
- A patch was published on 2026-07-09: Version 1.9.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48862 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48862?
- 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 is an unbounded resource allocation (CWE-770) in Mint's HTTP/2 implementation. Specifically, the `handle_push_promise/3` function in `lib/mint/http2.ex` inserts a `:reserved_remote` entry into the connection's stream map for every inbound `PUSH_PROMISE` frame without checking the `max_concurrent_streams` setting. Because the concurrency limit is only enforced when the subsequent `HEADERS` frame arrives, an attacker can flood the client with promises and withhold the headers, causing linear memory growth until the BEAM process crashes. The attack requires no authentication and is possible because HTTP/2 server push is enabled by default in Mint. The issue is fixed in version 1.9.0.
Affected products
- elixir-mint mint >= 0.2.0, < 1.9.0
Identifiers
- CVE-2026-48862
- GHSA-g586-ccqf-7x4r
Timeline
- 2026-06-02: disclosed: NVD and original report date
- 2026-07-09: advisory: GitHub Advisory published
- 2026-07-09: patched: Version 1.9.0 released