The Chrome team is delighted to announce the promotion of Chrome 49 to the stable channel for Windows, Mac and Linux.
Chrome 49.0.2623.75 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 49.
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 26 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
[$8000] High CVE-2016-1630: Same-origin bypass in Blink. Credit to Mariusz Mlynski.
[$7500] High CVE-2016-1631: Same-origin bypass in Pepper Plugin. Credit to Mariusz Mlynski.
[$5000] High CVE-2016-1632: Bad cast in Extensions. Credit to anonymous.
[$3000] High CVE-2016-1633: Use-after-free in Blink. Credit to cloudfuzzer.
[$3000] High CVE-2016-1634: Use-after-free in Blink. Credit to cloudfuzzer.
[$2000] High CVE-2016-1635: Use-after-free in Blink. Credit to Rob Wu.
[$2000] High CVE-2016-1636: SRI Validation Bypass. Credit to [email protected].
[$500] High CVE-2015-8126: Out-of-bounds access in libpng. Credit to joerg.bornemann.
[$2000] Medium CVE-2016-1637: Information Leak in Skia. Credit to Keve Nagy.
[$1000] Medium CVE-2016-1638: WebAPI Bypass. Credit to Rob Wu.
[$1000] Medium CVE-2016-1639: Use-after-free in WebRTC. Credit to Khalil Zhani.
[$1000] Medium CVE-2016-1640: Origin confusion in Extensions UI. Credit to Luan Herrera.
[$500] Medium CVE-2016-1641: Use-after-free in Favicon. Credit to Atte Kettunen of OUSPG.
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. An additional $14,500 in rewards were issued for security bugs present on non-stable channels.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
-  CVE-2016-1642: Various fixes from internal audits, fuzzing and other initiatives.
- Multiple vulnerabilities in V8 fixed at the tip of the 4.9 branch (currently 4.9.385.26).
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer or Control Flow Integrity.
Interested in switching release channels? Find out how. 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.
Krishna GovindGoogle Chrome