As usual Chrome 50 contains a number of fixes and improvements, but the biggest change in this latest version is the end of support for Windows XP, Windows Vista, and OS X 10.8 or older operating systems.
Bugs in the Universal XSS, Pdfium JPEG2000 decoding, and out-of-bound writes in V8 have been solved by external researchers claiming rewards which add up to $32K+. Internally, Google has secured fixes from internal audits, fuzzing and other initiatives.
Chrome is designed to be fast in every possible way: It's quick to start up from your desktop, loads web pages in a snap, and runs complex web applications fast. Learn more about Chrome and speed.
Chrome's browser window is streamlined, clean and simple. Chrome also includes features that are designed for efficiency and ease of use. For example, you can search and navigate from the same box, and arrange tabs however you wish — quickly and easily.
Chrome is designed to keep you safer and more secure on the web with built-in malware and phishing protection, autoupdates to make sure the browser is up-to-date with the latest security updates, and more. Learn more about Chrome's security features.
And more features
Chrome has many useful features built in, including extensions, translation in the browser, themes, and more. Learn more about Chrome's newest and most-loved features.
Chrome 51.0.2704.63 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 51.
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 42 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
- [$7500] High CVE-2016-1672: Cross-origin bypass in extension bindings. Credit to Mariusz Mlynski.
- [$7500] High CVE-2016-1673: Cross-origin bypass in Blink. Credit to Mariusz Mlynski.
- [$7500] High CVE-2016-1674: Cross-origin bypass in extensions. Credit to Mariusz Mlynski.
- [$7500] High CVE-2016-1675: Cross-origin bypass in Blink. Credit to Mariusz Mlynski.
- [$7500] High CVE-2016-1676: Cross-origin bypass in extension bindings. Credit to Rob Wu.
- [$4000] Medium CVE-2016-1677: Type confusion in V8. Credit to Guang Gong of Qihoo 360.
- [$3500] High CVE-2016-1678: Heap overflow in V8. Credit to Christoph Diehl.
- [$3500] High CVE-2016-1679: Heap use-after-free in V8 bindings. Credit to Rob Wu.
- [$3000] High CVE-2016-1680: Heap use-after-free in Skia. Credit to Atte Kettunen of OUSPG.
- [$3000] High CVE-2016-1681: Heap overflow in PDFium. Credit to Aleksandar Nikolic of Cisco Talos.
- [$1000] Medium CVE-2016-1682: CSP bypass for ServiceWorker. Credit to kingstonmailbox.
- [$1000] Medium CVE-2016-1683: Out-of-bounds access in libxslt. Credit to Nicolas Gregoire.
- [$1000] Medium CVE-2016-1684: Integer overflow in libxslt. Credit to Nicolas Gregoire.
- [$1000] Medium CVE-2016-1685: Out-of-bounds read in PDFium. Credit to Ke Liu of Tencent's Xuanwu LAB.
- [$1000] Medium CVE-2016-1686: Out-of-bounds read in PDFium. Credit to Ke Liu of Tencent's Xuanwu LAB.
- [$1000] Medium CVE-2016-1687: Information leak in extensions. Credit to Rob Wu.
- [$1000] Medium CVE-2016-1688: Out-of-bounds read in V8. Credit to Max Korenko.
- [$1000] Medium CVE-2016-1689: Heap buffer overflow in media. Credit to Atte Kettunen of OUSPG.
- [$1000] Medium CVE-2016-1690: Heap use-after-free in Autofill. Credit to Rob Wu.
- [$500] Low CVE-2016-1691: Heap buffer-overflow in Skia. Credit to Atte Kettunen of OUSPG.
- [$500] Low CVE-2016-1692: Limited cross-origin bypass in ServiceWorker. Credit to Til Jasper Ullrich.
- [$500] Low CVE-2016-1693: HTTP Download of Software Removal Tool. Credit to jackwillzac.
- [$500] Low CVE-2016-1694: HPKP pins removed on cache clearance. Credit to Ryan Lester.
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-1695: Various fixes from internal audits, fuzzing and other initiatives.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity or LibFuzzer.