Chrome 158 Patches 204 Vulnerabilities Including Six Critical Flaws
Google's Chrome 158 stable release patches 204 vulnerabilities, including six critical memory-safety bugs across rendering, GPU and media components. The volume and bug classes make the update important for any device running Chrome, even though no active exploitation has been reported.
Google shipped Chrome 158 to the stable channel on Tuesday, closing 204 security defects in the browser. The update includes six critical-severity flaws: three use-after-free bugs in WebView, GarbageCollection and WebAudio; two out-of-bounds write defects in GPU and ANGLE; and a buffer overflow in Media. The fixed builds are 158.0.8127.36 and.37 for Windows and macOS, and 158.0.8127.36 for Linux.
SecurityWeek reported the breakdown: 51 use-after-free issues, 34 incorrect authorization flaws, 16 missing authorization bugs, 15 out-of-bounds read or write defects, 14 uninitialized resource problems, 11 information leaks, 10 UI misrepresentation issues, nine improper input validation flaws and eight race conditions. Google and Xinyang Ge reported 145 and 15 bugs. No bounty was paid for 163 flaws. Google's release note also says amounts for 36 external reports were undetermined.
The release volume is unusual for a single stable-channel update, and the concentration of memory-safety bugs matters because Chrome's renderer, GPU stack and media pipeline are exposed to web content. Use-after-free, out-of-bounds writes and buffer overflows are classes that can turn crafted pages into crashes or worse. Google's note does not say any flaw is being exploited, and no bounty was paid for the six critical items, a pattern that can indicate internal fixes rather than reported external discoveries.
For users, the practical exposure is broad: Chrome runs on desktops, laptops and mobile devices, often carrying sign-in states for email, banking and corporate tools. Updating to 158 removes the patched paths; the public disclosure gives defenders and researchers a map of the fixed weaknesses. The source gives no confirmed active exploitation, but the update is the control point, and the version numbers identify the exact builds that contain the fixes.
Chrome users are affected because the patched flaws sit in widely exposed browser components; installing version 158 closes the disclosed paths. No confirmed active exploitation is reported, but the update is the practical mitigation.
Sources (1)
- [1]Original source(https://www.securityweek.com/chrome-158-patches-204-vulnerabilities/)