It looks like Microsoft might have to roll out the next Edge update sooner than they might have planned. A recent advisory clearly states multiple vulnerabilities affect Edge versions older than 149.0.4022.53. The official guidance tells everyone to update to that exact build or newer immediately to stay protected.

I checked the stable Edge version on my Mac and it’s stuck on version 149.0.4022.52. And clicking the check for updates button doesn’t help since it insists my browser is completely up-to-date.

This checks out with Microsoft’s own release notes page for Edge. The .52 build went live on June 4 and is currently still listed as the latest version.

The newer June 10 security warning by HKCERT specifically raises the safe threshold to .53. These newly disclosed flaws are serious. The advisory mentions vulnerabilities allowing remote code execution, security restriction bypass, and elevation of privilege. Attackers could potentially run malicious scripts or gain deeper system access.

HKCERT flags issues like CVE‑2026‑10883 and CVE‑2026‑10892 in this batch, with the first one tied to a critical Chromium flaw in ANGLE where a crafted page can trigger heap corruption. In plain terms, that’s the kind of low-level browser problem attackers can sometimes turn into full code execution if you’re unlucky, which is why security teams are now pointing users at 149.0.4022.53 or later instead of staying on .52.

You might assume you are fully patched because your browser updated a few days ago. You need to verify the actual version number yourself. Open the three-dot menu in Edge, navigate to Settings, and click About Microsoft Edge. Look right at the end of that long string of numbers.

If you don’t have the .53 build, which is most likely at the time of this writing, you can manually check for newer updates in the next few days.

Right now, many of us are stuck waiting for Microsoft to actually ship 149.0.4022.53 to our devices so we can match the version HKCERT is now recommending.

Meanwhile, Google, for its part, had already rolled out a Chrome update on June 2 to address these vulnerabilities.

The post Check your Microsoft Edge version after this new security warning appeared first on PiunikaWeb.