Hi everyone! We've just released Chrome Beta 86 (86.0.4240.68) for Android: it's now available on Google Play.You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.

If you find a new issue, please let us know by 
filing a bug.

Krishna Govind
Google Chrome

   Hi everyone! We've just released Chrome Beta 86 (86.0.4240.68) for Android: it's now available on Google Play.

You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.

If you find a new issue, please let us know by filing a bug.

Krishna Govind
Google Chrome

Hi, everyone! We've released Chrome Beta 86 (86.0.4240.68) for iOS: it'll become available on App Store in next few days.
You can see a partial list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Bindu Suvarna
Google Chrome

Hi, everyone! We've released Chrome Beta 86 (86.0.4240.68) for iOS: it'll become available on App Store in next few days.


You can see a partial list of the changes in the 
Git log. If you find a new issue, please let us know by filing a bug.

Bindu Suvarna
Google Chrome




Google Chrome
Prudhvikumar Bommana




Google Chrome
Krishna Govind

Google Chrome
Share on Twitter Share on Facebook

Share on Twitter Share on Facebook

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. 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.

This update includes 10 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.



[$15000][1100136] High CVE-2020-15960: Out of bounds read in storage. Reported by Anonymous on 2020-06-28

[$15000][1114636] High CVE-2020-15961: Insufficient policy enforcement in extensions. Reported by David Erceg on 2020-08-10

[$10000][1121836] High CVE-2020-15962: Insufficient policy enforcement in serial. Reported by Leecraso and Guang Gong of 360 Alpha Lab working with 360 BugCloud on 2020-08-26

[$5000][1113558] High CVE-2020-15963: Insufficient policy enforcement in extensions. Reported by David Erceg on 2020-08-06

[$TBD][1126249] High CVE-2020-15965: Out of bounds write in V8. Reported by Lucas Pinheiro, Microsoft Browser Vulnerability Research on 2020-09-08

[$TBD][1113565] Medium CVE-2020-15966: Insufficient policy enforcement in extensions. Reported by David Erceg on 2020-08-06

[$TBD][1121414] Low CVE-2020-15964: Insufficient data validation in media. Reported by Woojin Oh(@pwn_expoit) of STEALIEN on 2020-08-25



As usual, our ongoing internal security work was responsible for a wide range of fixes:

  • [1130676] Various fixes from internal audits, fuzzing and other initiatives


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.


Google Chrome

Srinivas Sista
Share on Twitter Share on Facebook


If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Cindy Bayless
Google Chrome OS
Share on Twitter Share on Facebook




Google Chrome
Prudhvikumar Bommana
Share on Twitter Share on Facebook

Google Chrome
Share on Twitter Share on Facebook


Marina Kazatcker
Google Chrome OS
Share on Twitter Share on Facebook

Share on Twitter Share on Facebook

Google Chrome
Share on Twitter Share on Facebook




Google Chrome
Prudhvikumar Bommana
Share on Twitter Share on Facebook

Share on Twitter Share on Facebook

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. 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.

This update includes 5 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$20000][1116304] High CVE-2020-6573: Use after free in video. Reported by Leecraso and Guang Gong of 360 Alpha Lab working with 360 BugCloud on 2020-08-14

[$10000][1102196] High CVE-2020-6574: Insufficient policy enforcement in installer. Reported by CodeColorist of Ant-Financial LightYear Labs on 2020-07-05

[$TBD][1081874] High CVE-2020-6575: Race in Mojo. Reported by Microsoft on 2020-05-12

[$TBD][1111737] High CVE-2020-6576: Use after free in offscreen canvas. Reported by Looben Yang on 2020-07-31

[$TBD][1122684] High CVE-2020-15959: Insufficient policy enforcement in networking. Reported by Eric Lawrence of Microsoft on 2020-08-27


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.


Google Chrome

Srinivas Sista
Share on Twitter Share on Facebook

A full list of changes in this build is available in the log. Interested in switching release channels?  Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.



Google Chrome
Prudhvikumar Bommana
Share on Twitter Share on Facebook