An IT administrator checks Microsoft Edge security updates and fleet-wide version status across office monitors.
Hong Kong's Computer Emergency Response Team Coordination Centre (HKCERT) has published another Microsoft Edge security bulletin. The bulletin is dated November 16, 2026, and the fix is simple: update Edge to version 157.0.4341.57 or later. If you manage a large Windows fleet, the harder part is confirming that every PC actually received that build.

HKCERT rates the bulletin Medium Risk and files it under client browsers. Its list of possible impacts is long. The agency says a remote attacker could exploit some of the vulnerabilities to cause denial of service, elevate privileges, bypass security restrictions, disclose sensitive information, execute code remotely or manipulate data.

An IT administrator checks Microsoft Edge security updates and fleet-wide version status across office monitors. What HKCERT reported​

The bulletin's key details are:

  • Affected: Microsoft Edge versions earlier than 157.0.4341.57
  • Fix: Update to 157.0.4341.57 or later
  • Risk rating: Medium
  • Possible impacts: Denial of service, remote code execution, security restriction bypass, data manipulation, information disclosure and elevation of privilege
  • Vulnerability identifiers: 71 CVE IDs, based on a direct count of the bulletin's list

The CVEs include three in the CVE-2026-1253xx range: CVE-2026-125342, CVE-2026-125344 and CVE-2026-125348. The other 68 run from CVE-2026-126840 through CVE-2026-126922, with gaps. HKCERT does not describe each vulnerability or say which impact belongs to which CVE.

Read the impact list carefully. HKCERT's wording is conditional. It says some of the vulnerabilities could lead to these outcomes. It does not say that every CVE allows remote code execution, that any CVE is being exploited, or that attack code is publicly available. The bulletin gives no individual severity scores, affected components or user-interaction requirements.

Summary: This is a large batch of browser fixes with one clear minimum version. The "remote code execution" label belongs to the batch as a whole and has not been confirmed for each CVE.

Microsoft's release notes confirm the build​

HKCERT's bulletin links to Microsoft's Edge security release notes. Those notes say Microsoft released Stable-channel Edge 157.0.4341.57 on November 13, 2026, and that it includes the latest Chromium security updates. HKCERT's bulletin followed three days later.

The Microsoft Update Catalog shows Edge Stable Channel Version 157 updates (Build 157.0.4341.57) for x86, x64 and ARM64 editions, each listed as last updated 11/12/2026. The one-day difference is probably just when the catalog entries were posted compared with the official announcement. Administrators who use the catalog for offline or staged deployments can get packages for all three Windows architectures.

The build has already been superseded. Microsoft's Stable Channel release notes list 157.0.4341.60, dated November 13, 2026, as the latest minor version of Edge 157. The Update Catalog also has a 157.0.4341.60 build. HKCERT says ".57 or later," so .60 also meets the threshold. Do not hold back a newer build in an attempt to land exactly on .57.

HKCERT's second Edge 157 bulletin​

This is not HKCERT's first Edge 157 bulletin. A week earlier, on November 9, HKCERT published a separate Medium Risk Edge bulletin. That one covered versions earlier than 157.0.4341.42 and listed seven CVEs: CVE-2026-119267 through CVE-2026-119272, plus CVE-2026-122518.

Edge 157 has had a busy month of security updates. According to Microsoft's security release notes:

Date (2026)ReleaseNote
November 5Stable 157.0.4341.42Chromium security updates
November 9Android/iOS 157.0.4341.42Mobile release
November 9Stable 157.0.4341.46Fix for CVE-2026-125350, which Chromium reported as exploited in the wild
November 11Android 157.0.4341.53Also includes the CVE-2026-125350 fix
November 13Stable 157.0.4341.57The build named in HKCERT's November 16 bulletin

CVE-2026-125350 is not part of the November 16 bulletin. Microsoft's notes say Chromium reported an in-the-wild exploit for it and that Stable 157.0.4341.46 included a fix. That CVE is not among the 71 identifiers in HKCERT's November 16 list, and nothing in the bulletin suggests any of its 71 CVEs are being exploited. The two issues are separate.

They do lead to the same action. A device on 157.0.4341.57 or later is also past the .46 build that Microsoft says fixed CVE-2026-125350. A machine that missed both updates has two reasons to install .57 or later.

Summary: Updating to 157.0.4341.57 or later covers both HKCERT bulletins. Edge 157 has had several security builds in less than two weeks.

Mobile, Extended Stable and other channels​

HKCERT's bulletin says "Microsoft Edge" and does not separate platforms or channels. Keep that in mind before you apply the desktop build number everywhere:

  • Android and iOS use different version numbers. Microsoft's notes list Edge for Android at 157.0.4341.53 on November 11 and Android/iOS at 157.0.4341.42 on November 9. There is no evidence that "157.0.4341.57" is the fixed build for mobile. Check each platform's app store and Microsoft's security guidance.
  • Extended Stable is a separate channel. The Update Catalog lists an Edge Extended Stable Channel Version 156 build, 156.0.4314.84, dated 11/12/2026. We could not confirm whether that build fixes the CVEs in this bulletin. If your organisation uses Extended Stable, check Microsoft's Security Update Guide instead of assuming that 156 fixes the same flaws.
  • Edge on macOS and Linux is on the same 157 release train, but HKCERT does not name individual operating systems. Use the version number to decide whether a machine needs updating.

How to update and verify Edge on a desktop​

Microsoft's support documentation describes this procedure:

  1. Open Microsoft Edge.
  2. Select Settings and more (the three-dot menu) in the upper-right corner.
  3. Go to Help and feedback, then select About Microsoft Edge. You can also type edge://settings/help in the address bar.
  4. Edge checks for updates and installs any it finds.
  5. If prompted, select Restart to finish the update.
  6. On the same About page, check that the version is 157.0.4341.57 or later.

Success looks like this: the About page reports a 157.0.4341.57 or later build and says Edge is up to date.

If the update stalls, Microsoft suggests two fallbacks:

  • Windows Update: On Windows, Edge updates may also arrive through Windows Update. Go to Start > Settings > Windows Update, select Check for updates, install what is available and restart if prompted.
  • Reinstall: If neither method works, download the current Edge installer from Microsoft and run it. Microsoft says favorites, passwords and settings are kept when Edge updates.

A common mistake is installing the update and then leaving Edge open for days. The fix is not complete until the browser restarts. On a laptop that sleeps but never reboots, an old Edge process can stay in memory for a long time.

Guidance for IT administrators​

Managed environments need more than an About page. Microsoft's Edge update policy documentation covers settings that allow automatic updates, allow only manual checks, or allow only automatic silent updates. It also warns that if you disable updates, you have to check for and distribute new versions yourself. That guidance is written for Windows devices joined to an Active Directory domain. Intune, other MDM tools and non-Windows platforms have their own configuration methods.

A practical checklist:

  • Check your update policy before assuming devices are patched. A policy someone set years ago for compatibility testing could be blocking this update now.
  • Report on versions, not just compliance status. Look for endpoints below 157.0.4341.57, and treat any still below .46 as a priority.
  • Account for every channel. Treat Stable, Extended Stable, Beta and Dev, plus mobile devices, as separate checks.
  • Remember that 157.0.4341.60 exists. Your rings may land on .60 instead of .57. Both meet HKCERT's threshold.

Microsoft is also adding tools for this. Release-tracking listings for the 157 build mention Security Update Alerts in the Edge management service, which let administrators pick a severity threshold and get alerts when an Edge update includes security fixes at or above it, including zero-day fixes. If you are tired of finding out about browser security fixes from CERT bulletins a few days late, it may be worth testing.

Analysis: is "Medium Risk" right?​

HKCERT's Medium rating sits next to an impact list that includes remote code execution and elevation of privilege. That can look inconsistent. HKCERT's bulletin does not explain how it chose the rating. A reasonable explanation is that the agency rates the overall picture, including no confirmed exploitation for these CVEs and an update that is already available, rather than the worst-case impact of any single flaw. That is our interpretation, not HKCERT's stated method.

The opposite view is also fair. The bulletin covers 71 CVEs in an application that processes untrusted internet content all day. Attackers can analyse a published patch to find the flaws it fixes, so the time between "patched" and "exploited" can be short. Chromium flaws have often moved from routine fix to active exploitation. Microsoft's own security notes show this repeatedly, including CVE-2026-125350 this month.

Our view as WindowsForum: whether the label is Medium or Critical, the action is the same. Update Edge to 157.0.4341.57 or later, restart it, and confirm the version. It takes about two minutes.

Key takeaways​

  • HKCERT's November 16, 2026 bulletin covers Edge versions earlier than 157.0.4341.57 and lists 71 CVEs, with possible impacts that include remote code execution and elevation of privilege.
  • Microsoft released Stable 157.0.4341.57 on November 13. A newer 157.0.4341.60 build is already out, and both meet the threshold.
  • The bulletin does not report exploitation of these 71 CVEs. The separate, exploited CVE-2026-125350 was fixed earlier in 157.0.4341.46.
  • Mobile and Extended Stable channels use different builds, so check them separately.
  • After updating, restart Edge and confirm the version on the About page.
 

References

  1. Microsoft Edge Multiple Vulnerabilities - Hong Kong Computer Emergency Response Team Coordination Centre Hong Kong Computer Emergency Response Team Coordination Centre Mon, 16 Nov 2026 01:57:19 GMT
  2. Microsoft Update Catalog catalog.update.microsoft.com
  3. Microsoft Edge Multiple Vulnerabilities hkcert.org