The Chrome team is delighted to announce the promotion of Chrome 58 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.
Chrome 58.0.3029.81 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 58.
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 29 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$3000] High CVE-2017-5057: Type confusion in PDFium. Credit to Guang Gong of Alpha Team, Qihoo 360
[$2000] High CVE-2017-5058: Heap use after free in Print Preview. Credit to Khalil Zhani
[$N/A] High CVE-2017-5059: Type confusion in Blink. Credit to SkyLined working with Trend Micro's Zero Day Initiative
[$2000] Medium CVE-2017-5060: URL spoofing in Omnibox. Credit to Xudong Zheng
[$2000] Medium CVE-2017-5061: URL spoofing in Omnibox. Credit to Haosheng Wang (@gnehsoah)
[$1500] Medium CVE-2017-5062: Use after free in Chrome Apps. Credit to anonymous
[$1000] Medium CVE-2017-5063: Heap overflow in Skia. Credit to Sweetchip
[$1000] Medium CVE-2017-5064: Use after free in Blink. Credit to Wadih Matar
[$500] Medium CVE-2017-5065: Incorrect UI in Blink. Credit to Khalil Zhani
[$500] Medium CVE-2017-5066: Incorrect signature handing in Networking. Credit to chenchu
[$500] Medium CVE-2017-5067: URL spoofing in Omnibox. Credit to Khalil Zhani
[$N/A] Low CVE-2017-5069: Cross-origin bypass in Blink. Credit to Michael Reizelman
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:
 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.