And a while back TH, given that it only affects 15.0.18.0 & prior and 15.0.23.0 has been out for a while...this is definitively old news.
No problem, aztony. The comment was made to reassure ESET users that all has been in hand for a while. ESET are very good when it comes to responsiveness to this sort of thing. It was not meant to be in any way derogatory to your efforts to inform. So apologies if that is how it came across.
Aztony's quote already said fix was released, and when is explained in the linked article. Still interesting even though it is fixed, AV's are an interesting target because the have system privileges and usually don't use the latest exploit mitigations on their own processes. Imho, ESET's responsiveness wasn't that fast btw: