Microsoft Edge: contain code execution

Published · Updated · Digital strategy · 4 min read · By Cyber Intelligence Embassy

At a glance

Microsoft Edge: remote code execution. This 2026-05-18 case examines 1 version entries and 76 CVEs, documented releases and checks suited to browsers, using CERTFR-2026-AVI-0607.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-05-18, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0607, published on 2026-05-18. Its scope includes Microsoft Edge. Reported consequences are remote code execution, impact requiring vendor clarification, security control bypass. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case focuses on Microsoft Edge. Locate that edition in live installations, deployment images and actual dependencies, rather than treating every product from Microsoft as equivalent.

Products and versions to examine

Reference
CERTFR-2026-AVI-0607
Source first published
2026-05-18
Latest source revision available for this day
2026-05-18
Named components
Microsoft Edge
CVE identifiers
CVE-2026-8554, CVE-2026-8559, CVE-2026-8547, CVE-2026-8542, CVE-2026-8562, CVE-2026-8513, CVE-2026-8560, CVE-2026-8534, CVE-2026-8531, CVE-2026-8578, CVE-2026-8565, CVE-2026-8536, CVE-2026-8587, CVE-2026-8571, CVE-2026-8556, CVE-2026-8543, CVE-2026-45494, CVE-2026-8557, CVE-2026-8538, CVE-2026-8526, CVE-2026-8523, CVE-2026-8549, CVE-2026-8530, CVE-2026-8541 … (+52)
ComponentPublished condition
Microsoft Edge< 148.0.3967.70

For Microsoft Edge, the published condition is “< 148.0.3967.70”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Microsoft Edge does not close this case.

Mechanism and prerequisites

Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.

The primary record CVE-2026-8554, published by Chrome, covers Chrome. The retained revision is dated 2026-05-15. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0607.

Choose the appropriate intervention

  1. Locate Microsoft Edge instances, running releases and service owners. Record condition < 148.0.3967.70 in the ticket alongside reference CERTFR-2026-AVI-0607.
  2. Compare the installed branch with the vendor’s Microsoft Edge release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Microsoft Edge, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Microsoft Edge: Close every Microsoft Edge process, restart the browser and capture its actual version. With a test profile, exercise an internal application and check approved extensions; verify any long-term maintenance branches separately. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0607: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Microsoft Edge?

Advisory CERTFR-2026-AVI-0607 states: Microsoft Edge — < 148.0.3967.70. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

What is still needed to assess Microsoft Edge exposure?

For Microsoft Edge, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0607 do not establish every prerequisite or active exploitation.

Sources and related reading

Practical guide : Review browser extensions before enterprise deployment

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0607
Advisory revision : · Checked on :

Affected systems · 1

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Microsoft Edge versions antérieures à 148.0.3967.70
CVE identifiers · 76