Source
Microsoft Security Response Center
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 98.0.1108.43 2/3/2022 98.0.4758.80
**What is the version information for this release?** Microsoft Edge Version Date Released Based on Chromium Version 97.0.1072.69 1/20/2022 97.0.4692.99
**What is the result of opting into the stricter verification behavior?** Opting into the stricter verification behavior causes the WinVerifyTrust function to perform strict Windows Authenticode signature verification for PE files. After you opt in, PE files will be considered "unsigned" if Windows identifies content in them that does not conform to the Authenticode specification. This may impact some installers. If you are using an installer that is impacted, Microsoft recommends using an installer that only extracts content from validated portions of the signed file. **How can I enable the new signature verification behavior?** Customers who would like to enable the new Authenticode signature verification behavior can do so by setting a key in the system registry. When the key is set, Windows Authenticode signature verification will no longer recognize binaries with Authenticode signatures that contain extraneous information in the WIN\_CERTIFICATE structure. Customers can choose ...
**Why is this Chrome CVE included in the Security Update Guide?** The vulnerability assigned to this CVE is in Chromium Open Source Software (OSS) which is consumed by Microsoft Edge (Chromium-based). It is being documented in the Security Update Guide to announce that the latest version of Microsoft Edge (Chromium-based) is no longer vulnerable. Please see Security Update Guide Supports CVEs Assigned by Industry Partners for more information. **How can I see the version of the browser?** 1. In your Microsoft Edge browser, click on the 3 dots (...) on the very right-hand side of the window 2. Click on **Help and Feedback** 3. Click on **About Microsoft Edge**
**Why is this Chrome CVE included in the Security Update Guide?** The vulnerability assigned to this CVE is in Chromium Open Source Software (OSS) which is consumed by Microsoft Edge (Chromium-based). It is being documented in the Security Update Guide to announce that the latest version of Microsoft Edge (Chromium-based) is no longer vulnerable. Please see Security Update Guide Supports CVEs Assigned by Industry Partners for more information. **How can I see the version of the browser?** 1. In your Microsoft Edge browser, click on the 3 dots (...) on the very right-hand side of the window 2. Click on **Help and Feedback** 3. Click on **About Microsoft Edge**