I'm not sure if this bug is related to Edge Android still using Chromium 77, which was released in September 2019. If so, then the refusal of the Edge Android team to move on to updated Chromium versions is starting to bite the browser in more ways than one. If not, then this security vulnerability should be fixed asap anyway.
(In any case, it's high time your Android team got off their butts and finally updated the Chromium version. A handful of months of delay may have been forgivable, a year and a quarter and counting is completely ridiculous. Not that it matters what I say, but I'm running out of patience on this matter.)