

High CVE-2021-21123: Insufficient data validation in File System API. High CVE-2021-21122: Use after free in Blink. Reported by Leecraso and Guang Gong of 360 Alpha Lab on High CVE-2021-21121: Use after free in Omnibox.

Reported by Nan and Guang Gong of 360 Alpha Lab on High CVE-2021-21120: Use after free in WebSQL. High CVE-2021-21119: Use after free in Media. Reported by Tyler Nighswander of Theori on High CVE-2021-21118: Insufficient data validation in V8. Critical CVE-2021-21117: Insufficient policy enforcement in Cryptohome. Please see the Chrome Security Page for more information. Below, we highlight fixes that were contributed by external researchers. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. If so, they need to create a new browser user profile.Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. When users relaunch Chrome, they might get a message that their profile is from a different version. Make sure all your users relaunch Chrome on their Windows computers after the downgrade is complete. Relaunch Chrome on a Windows computer and check the version to make sure the downgrade was successful. Otherwise, enter msiexec /i GoogleChromeStandaloneEnterprise.msi ALLOWDOWNGRADE=1 To downgrade to the version that you last manually installed using the MSI file, enter msiexec /fvomus GoogleChromeStandaloneEnterprise.msi ALLOWDOWNGRADE=1 Don’t forget to turn on auto-updates again after your issue is resolved. To prevent Windows computers from automatically updating Chrome shortly after the downgrade, temporarily halt auto-updates.They're not used for data other than Chrome data.They're not set to the root of a volume, such as D:\.If you use the UserDataDir or DiskCacheDir policy settings to override default locations, check to make sure that:.You can downgrade to the previous stable version of Chrome.
