Security Issues Fixed In Chrome Browser New Update

Googlehas updated the Chrome browser with a round of security fixes, which patches up three critical issues.

Google updated the Chrome browser with a round of security fixes, which patches up three critical issues.
As per the post on eth Chrome releases blog, the latest stable release for Chrome version 49.0.2623.87 for Windows, Mac, and Linux, includes fixes for numerous vulnerabilities, which were discovered by security research.
The disclaimer provided by Google in its official blog states,
“The stable channel has been updated to 49.0.2623.87 for Windows, Mac, and Linux.
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 3 security fixes that were contributed by external researchers. Please see the Chromium security page for more information.
[$5000][589838] High CVE-2016-1643: Type confusion in Blink. Credit to cloudfuzzer.
[$3500][590620] High CVE-2016-1644: Use-after-free in Blink. Credit to Atte Kettunen of OUSPG.
[587227] High CVE-2016-1645: Out-of-bounds write in PDFium. Credit to anonymous working with HP's Zero Day Initiative.”
The first major security issue, CVE-2016-164, is a typeof confusion vulnerability which impacts Blink, a well known engine used by Google Chrome. The researcher was awarded $5000 for the submission of their findings.
The second critical flaw, CVE-2016-1644, also affects Blink. This security issue is a use-after free vulnerability, a memory corruption problem, which would allow attackers to execute remote code. This issue has been serious enough to allow the researcher to earn an award of $3500.
The third major issue, CVE-2016-1645, is an out of bounds write issue in PDFium, Google’s PDF library that was set to the open-source community in 2014. This issue was discovered by a researcher who was working alongside HP’S Zero Day Initiative, and if a reward is involved, then it has yet not been revealed.
For more information check Chromium security page