CVE-2026-49754
HTTP/2 CONTINUATION flood causes Mint client memory exhaustion.
Is CVE-2026-49754 being exploited?
Not confirmed. CVE-2026-49754 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-49754?
CVE-2026-49754 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49754?
Yes. A fix has been recorded for CVE-2026-49754. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49754 affect?
CVE-2026-49754 affects elixir-mint Mint <= 1.8.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49754?
Upgrade Mint to >= 1.9.0
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory exhaustion of Mint client via endless inbound CONTINUATION frames -> BEAM process crash/DoS.
Patch when possible
- affected>= 0.1.0 and < 1.9.0
- affected>= 596ca4304504be68939c4929e0831557097962b8 and < b662d127d3028b5426c88d4c9cc7fe430491a10b
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.