Chrome 48.0.2564.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 48.
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 37 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
[$3000] High CVE-2016-1612: Bad cast in V8. Credit to cloudfuzzer.
[$3000] High CVE-2016-1613: Use-after-free in PDFium. Credit to anonymous.
[$2000] Medium CVE-2016-1614: Information leak in Blink. Credit to Christoph Diehl.
[$500] Medium CVE-2016-1615: Origin confusion in Omnibox. Credit to Ron Masas.
[$500] Medium CVE-2016-1616: URL Spoofing. Credit to Luan Herrera.
[$500] Medium CVE-2016-1617: History sniffing with HSTS and CSP. Credit to jenuis.
[$500] Medium CVE-2016-1618: Weak random number generator in Blink. Credit to Aaron Toponce.
[$500] Medium CVE-2016-1619: Out-of-bounds read in PDFium. Credit to Keve Nagy.
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. The total value of additional rewards and their recipients will updated here when all reports have gone through the reward panel.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
-  CVE-2016-1620: Various fixes from internal audits, fuzzing and other initiatives.
- Multiple vulnerabilities in V8 fixed at the tip of the 4.8 branch (currently 4.8.271.17).
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer or Control Flow Integrity.
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.