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 53.0.2785.116 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 53.
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 33 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-5147: Universal XSS in Blink. Credit to anonymous
- [$7500] High CVE-2016-5148: Universal XSS in Blink. Credit to anonymous
- [$7500] High CVE-2016-5149: Script injection in extensions. Credit to Max Justicz (http://web.mit.edu/maxj/www/)
- [$5000] High CVE-2016-5150: Use after free in Blink. Credit to anonymous
- [$5000] High CVE-2016-5151: Use after free in PDFium. Credit to anonymous
- [$5000] High CVE-2016-5152: Heap overflow in PDFium. Credit to GiWan Go of Stealien
- [$3500] High CVE-2016-5153: Use after destruction in Blink. Credit to Atte Kettunen of OUSPG
- [$3000] High CVE-2016-5154: Heap overflow in PDFium. Credit to anonymous
- [$3000] High CVE-2016-5155: Address bar spoofing. Credit to anonymous
- [$3000] High CVE-2016-5156: Use after free in event bindings. Credit to jinmo123
- [$TBD] High CVE-2016-5157: Heap overflow in PDFium. Credit to anonymous
- [$TBD] High CVE-2016-5158: Heap overflow in PDFium. Credit to GiWan Go of Stealien
- [$TBD] High CVE-2016-5159: Heap overflow in PDFium. Credit to GiWan Go of Stealien
- [$n/a] Medium CVE-2016-5161: Type confusion in Blink. Credit to 62600BCA031B9EB5CB4A74ADDDD6771E working with Trend Micro's Zero Day Initiative
- [$n/a] Medium CVE-2016-5162: Extensions web accessible resources bypass. Credit to Nicolas Golubovic
- [$3000] Medium CVE-2016-5163: Address bar spoofing. Credit to Rafay Baloch PTCL Etisalat (http://rafayhackingarticles.net)
- [$2000] Medium CVE-2016-5164: Universal XSS using DevTools. Credit to anonymous
- [$1000] Medium CVE-2016-5165: Script injection in DevTools. Credit to Gregory Panakkal
- [$TBD] Medium CVE-2016-5166: SMB Relay Attack via Save Page As. Credit to Gregory Panakkal
- [$500] Low CVE-2016-5160: Extensions web accessible resources bypass. Credit to @l33terally, FogMarks.com (@FogMarks)
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-5167: Various fixes from internal audits, fuzzing and other initiatives.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity or LibFuzzer.