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.

Speed

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.

Simplicity

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.

Security

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.

What's New:

Chrome 52.0.2743.82 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 52.

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 48 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.

  • [$15000][610600] High CVE-2016-1706: Sandbox escape in PPAPI. Credit to Pinkie Pie
  • [$3000][622183] High CVE-2016-1707: URL spoofing on iOS. Credit to xisigr of Tencent's Xuanwu Lab
  • [$TBD][613949] High CVE-2016-1708: Use-after-free in Extensions. Credit to Adam Varsan
  • [$TBD][614934] High CVE-2016-1709: Heap-buffer-overflow in sfntly. Credit to ChenQin of Topsec Security Team
  • [$TBD][616907] High CVE-2016-1710: Same-origin bypass in Blink. Credit to Mariusz Mlynski
  • [$TBD][617495] High CVE-2016-1711: Same-origin bypass in Blink. Credit to Mariusz Mlynski
  • [$TBD][618237] High CVE-2016-5127: Use-after-free in Blink. Credit to cloudfuzzer
  • [$TBD][619166] High CVE-2016-5128: Same-origin bypass in V8. Credit to Anonymous
  • [$TBD][620553] High CVE-2016-5129: Memory corruption in V8. Credit to Jeonghoon Shin
  • [$TBD][623319] High CVE-2016-5130: URL spoofing. Credit to Wadih Matar
  • [$TBD][623378] High CVE-2016-5131: Use-after-free in libxml. Credit to Nick Wellnhofer
  • [$1000][607543] Medium CVE-2016-5132: Limited same-origin bypass in Service Workers. Credit to Ben Kelly
  • [$1000][613626] Medium CVE-2016-5133: Origin confusion in proxy authentication. Credit to Patch Eudor
  • [$500][593759] Medium CVE-2016-5134: URL leakage via PAC script. Credit to Paul Stone
  • [$500][605451] Medium CVE-2016-5135: Content-Security-Policy bypass. Credit to kingxwy
  • [$TBD][625393] Medium CVE-2016-5136: Use after free in extensions. Credit to Rob Wu
  • [$TBD][625945] Medium CVE-2016-5137: History sniffing with HSTS and CSP. Credit to Xiaoyin Liu

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:

  • [629852] CVE-2016-1705: Various fixes from internal audits, fuzzing and other initiatives.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer,Control Flow Integrity or LibFuzzer.