CVE-2026-49754

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood).

When Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity).

A malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient.

This issue affects mint: from 0.1.0 before 1.9.0.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-49754
github Patch Available🟡 PoC Available

Unbounded CONTINUATION/HEADERS frame accumulation (CONTINUATION flood) · Advisory · elixir-mint/mint · GitHub

https://github.com/elixir-mint/mint/security/advisories/GHSA-2p26-p43x-fhp8
github_commit

commit b662d127d302 (elixir-mint/mint)

Fix landed in elixir-mint/mint commit b662d127d302 — awaiting tagged release

https://github.com/elixir-mint/mint/commit/b662d127d3028b5426c88d4c9cc7fe430491a10b
generic

HTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-49754.html

Vendor Advisories for CVE-2026-49754(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
mint0.1.0 ... 1.8.0 (23 versions)1.9.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:49 UTCEG score recompute
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 00:06 UTCOSV refresh
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 03:45 UTCEG score recompute
  20. 2026-08-23 13:42 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 23:19 UTCEG score recompute
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 10:11 UTCEG score recompute
Show 75 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 16:22 UTCEG score recompute
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 03:38 UTCEG score recompute
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 15:02 UTCEG score recompute
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-13 23:17 UTCEG score recompute
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 16:39 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 15:23 UTCEG score recompute
  15. 2026-08-11 02:46 UTCEG score recompute
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 01:32 UTCEG score recompute
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 00:19 UTCEG score recompute
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 23:05 UTCEG score recompute
  22. 2026-08-06 21:52 UTCEG score recompute
  23. 2026-08-06 13:47 UTCEPSS rescore
  24. 2026-08-05 20:36 UTCEG score recompute
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 19:55 UTCEG score recompute
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:39 UTCEPSS rescore
  29. 2026-08-03 15:55 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 14:39 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 13:25 UTCEG score recompute
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-07-31 05:38 UTCEG score recompute
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-29 10:52 UTCEG score recompute
  39. 2026-07-28 15:37 UTCEPSS rescore
  40. 2026-07-28 03:40 UTCEG score recompute
  41. 2026-07-26 22:56 UTCEG score recompute
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-24 14:18 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:18 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-20 17:08 UTCEPSS rescore
  50. 2026-07-19 14:31 UTCEPSS rescore
  51. 2026-07-19 14:31 UTCEPSS rescore
  52. 2026-07-19 02:29 UTCEPSS rescore
  53. 2026-07-18 10:04 UTCEPSS rescore
  54. 2026-07-16 17:03 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-13 22:30 UTCEPSS rescore
  59. 2026-07-13 06:13 UTCEPSS rescore
  60. 2026-07-12 05:46 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-08 15:16 UTCEPSS rescore
  64. 2026-07-07 13:46 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-05 02:30 UTCEPSS rescore
  68. 2026-07-04 06:31 UTCEPSS rescore
  69. 2026-07-01 15:07 UTCEPSS rescore
  70. 2026-06-30 23:22 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-27 03:08 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-49754?
CVE-2026-49754 is a high vulnerability published on June 2, 2026. Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood). When Mint's HTTP/2 receive path observes a HEADERS frame without the ENDHEADERS flag, the unparsed…
When was CVE-2026-49754 disclosed?
CVE-2026-49754 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49754 actively exploited?
CVE-2026-49754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.1% of all scored CVEs.
What is the CVSS score of CVE-2026-49754?
CVE-2026-49754 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-49754?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49754, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49754

Explore →

Is Your Infrastructure Affected by CVE-2026-49754?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs