The Chrome team is delighted to announce the promotion of Chrome 50 to the stable channel for Windows, Mac and Linux.

blog posts about new features and big efforts delivered in 50.

Chrome 50.0.2661.75 contains a number of fixes and improvements -- a list of changes is available in the

Security Fixes and Rewards

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 20 security fixes . Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.

[$7500][ 590275 ] High CVE-2016-1652: Universal XSS in extension bindings. Credit to anonymous.

[$5000][ 589792 ] High CVE-2016-1653: Out-of-bounds write in V8. Credit to Choongwoo Han.

[ 591785 ] Medium CVE-2016-1651: Out-of-bounds read in Pdfium JPEG2000 decoding. Credit to kdot working with HP's Zero Day Initiative.

[$1500][ 589512 ] Medium CVE-2016-1654: Uninitialized memory read in media. Credit to Atte Kettunen of OUSPG.

[$1500][ 582008 ] Medium CVE-2016-1655: Use-after-free related to extensions. Credit to Rob Wu.

[$500][ 570750 ] Medium CVE-2016-1656: Android downloaded file path restriction bypass. Credit to Dzmitry Lukyanenko .

[$1000][ 567445 ] Medium CVE-2016-1657: Address bar spoofing. Credit to Luan Herrera.

[$500][ 573317 ] Low CVE-2016-1658: Potential leak of sensitive information to malicious extensions. Credit to Antonio Sanso (@asanso) of Adobe.

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. The total value of additional rewards and their recipients will updated here when all reports have gone through the reward panel.

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

[ 602697 ] CVE-2016-1659: Various fixes from internal audits, fuzzing and other initiatives.

Many of our security bugs are detected using

AddressSanitizer

,

MemorySanitizer

,

Control Flow Integrity

or

LibFuzzer

.



