"Chrome 148 also includes patches for over 30 high-severity vulnerabilities, most of which are use-after-free bugs impacting ANGLE, SVG, DOM, Fullscreen, Views, Aura, GPU, Skia, Passwords, ServiceWorker, Chromoting, WebRTC, PresentationAPI, and MediaRecording."
"The first critical flaw is an integer overflow issue in Blink, tracked as CVE-2026-7896. It could allow remote attackers to exploit a heap memory corruption via a crafted HTML page. According to Google's advisory, a $43,000 bug bounty reward was paid to the researcher who reported the flaw in mid-March."
"Per Google's advisory, the highest bug bounty was paid for an out-of-bounds read and write issue in the V8 JavaScript engine. Project WhatForLunch received a $55.000 reward for the finding."
Chrome 148 has been promoted to the stable channel with 127 security patches addressing multiple vulnerability severity levels. Three critical-severity flaws were fixed, including an integer overflow in Blink (CVE-2026-7896) that could enable heap memory corruption through malicious HTML, and two use-after-free weaknesses in Mobile and Chromoting components (CVE-2026-7897 and CVE-2026-7898). Over 30 high-severity vulnerabilities were patched, predominantly use-after-free bugs affecting various components including ANGLE, SVG, DOM, GPU, and WebRTC. Additional high-severity issues included heap buffer overflows, out-of-bounds memory access, and integer overflows. More than 60 medium-severity flaws and remaining low-severity weaknesses were also addressed. Google paid $138,000 in bug bounty rewards to external researchers, with the highest single reward being $55,000 for a V8 JavaScript engine vulnerability.
Read at SecurityWeek
Unable to calculate read time
Collection
[
|
...
]