The Chrome team is delighted to announce the promotion of Chrome 54 to the stable channel - 54.0.2840.59 for Windows, Mac, and Linux. This will roll out over the coming days/weeks.
Chrome 54.0.2840.59 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 54.
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 21 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$7500] High CVE-2016-5181: Universal XSS in Blink. Credit to Anonymous
[$5500] High CVE-2016-5182: Heap overflow in Blink. Credit to Giwan Go of STEALIEN
[$3000] High CVE-2016-5183: Use after free in PDFium. Credit to Anonymous
[$3000] High CVE-2016-5184: Use after free in PDFium. Credit to Anonymous
[$3000] High CVE-2016-5185: Use after free in Blink. Credit to cloudfuzzer
[$1000] High CVE-2016-5187: URL spoofing. Credit to Luan Herrera
[$3133.7] Medium CVE-2016-5188: UI spoofing. Credit to Luan Herrera
[$500] Medium CVE-2016-5189: URL spoofing. Credit to xisigr of Tencent's Xuanwu Lab
[$500] Medium CVE-2016-5186: Out of bounds read in DevTools. Credit to Abdulrahman Alqabandi (@qab)
[$500] Medium CVE-2016-5191: Universal XSS in Bookmarks. Credit to Gareth Hughes
[$N/A] Medium CVE-2016-5190: Use after free in Internals. Credit to Atte Kettunen of OUSPG
[$500] Low CVE-2016-5193: Scheme bypass. Credit to Yuyang ZHOU (martinzhou96)
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.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
-  CVE-2016-5194: Various fixes from internal audits, fuzzing and other initiatives
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity, or libFuzzer.
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.
Richard BustamanteGoogle Chrome