Upstream has released version 52.0.2743.116 on August 3: http://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html This fixes several new security issues. This is the current version in the stable channel: http://googlechromereleases.blogspot.com/search/label/Stable%20updates
Packages are available for testing: MGA5 SRPM: chromium-browser-stable-52.0.2743.116-1.mga5.src.rpm RPMS: chromium-browser-stable-52.0.2743.116-1.mga5.i586.rpm chromium-browser-52.0.2743.116-1.mga5.i586.rpm chromium-browser-stable-52.0.2743.116-1.mga5.x86_64.rpm chromium-browser-52.0.2743.116-1.mga5.x86_64.rpm Advisory: Chromium-browser-stable 52.0.2743.116 fixes security issues: two heap overflow issues in pdfium (CVE-2016-5139 and CVE-2016-5140); an address bar spoofing problem (CVE-2016-5141); a use-after-free bug (CVE-2016-5142) and a same origin bypass problem (CVE-2016-5145) in blink; two parameter sanitization failures in DevTools (CVE-2016-5143 and CVE-2016-5144); and various fixes from upstream's internal audits, fuzzing, and other initiatives (CVE-2016-5146). References: http://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5139 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5140 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5141 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5142 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5143 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5144 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5145 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5146
CC: (none) => cjwAssignee: cjw => qa-bugs
tested mga5-64 general browsing, jetstream, acid3, youtube video all OK.
CC: (none) => wrw105Whiteboard: (none) => has_procedure mga5-64-ok
Keywords: (none) => validated_updateWhiteboard: has_procedure mga5-64-ok => has_procedure mga5-64-ok advisoryCC: (none) => davidwhodgins, sysadmin-bugs
URL: (none) => http://lwn.net/Vulnerabilities/696700/
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0279.html
Status: NEW => RESOLVEDResolution: (none) => FIXED