Google has begun rolling out Chrome 158 with fixes for 204 security vulnerabilities, including six rated critical. The release addresses a broad mix of memory-safety and access-control weaknesses, and Google advises users to update promptly. The company has not reported that any of the flaws are being exploited in the wild, but the size of the patch set makes the update relevant to both individual users and organizations managing fleets of browsers.
A wide-ranging set of fixes
The six critical issues span several components of the browser. Three are use-after-free vulnerabilities involving WebView, GarbageCollection and WebAudio. The remaining critical flaws include out-of-bounds write defects in GPU and ANGLE, as well as a buffer overflow in Media. Such memory-handling errors can create security risks when software processes data in unexpected ways; the source announcement does not provide details about specific exploitation scenarios for these bugs.
The other vulnerabilities comprise 62 high-severity issues, 82 medium-severity issues and 54 low-severity issues. Use-after-free was the most frequently identified vulnerability class, with 51 instances. The update also addresses 34 incorrect-authorization flaws and 16 missing-authorization issues. Other categories include 15 out-of-bounds reads or writes, 14 cases involving uninitialized resources, 11 information leaks, 10 instances of user-interface misrepresentation, nine input-validation problems and eight race conditions.
Discovery and bug bounty details
Google credited its own researchers with finding 145 of the vulnerabilities, while Xinyang Ge discovered 15. The announcement says no bounty will be paid for 163 of the flaws. Google awarded a total of $11,000 for five vulnerabilities reported by external researchers and had not yet determined bounty amounts for another 36. Those figures account for the full set of 204 issues, though the announcement does not detail the individual bounty amounts or provide further attribution for every flaw.
The range of defect types illustrates how a browser update can involve more than one isolated component. Chrome processes web content through multiple areas, including media handling, graphics and embedded web experiences. Authorization weaknesses, meanwhile, concern whether access is correctly permitted or denied. The patch list therefore reflects fixes across different parts of the software, rather than a single vulnerability pattern. The release information does not describe the underlying code changes or provide a technical assessment of each issue.
What users and IT teams should do
Chrome 158 is rolling out as versions 158.0.8127.36 and 158.0.8127.37 for Windows and macOS, and version 158.0.8127.36 for Linux. Users should check that their browser has received the applicable release and complete the update. Because distribution is described as a rollout, availability may not be simultaneous across every installation. Google’s recommendation to update as soon as possible is particularly relevant given the number and severity of the flaws addressed.
For businesses, the release is also a device-management task. IT teams can use their established browser update processes to identify managed devices that have not yet moved to the patched version, coordinate deployment across their environments and verify that updates have taken effect. Organizations should follow their own change-control and endpoint-management policies, while avoiding unnecessary delays for a security update of this scale. The source does not identify a separate workaround or say that administrators need to take steps beyond updating Chrome.
No exploitation reported
Google made no mention of the vulnerabilities being exploited in real-world attacks. That is useful context, but it does not remove the need to install the fixes: the release addresses critical as well as high-, medium- and low-severity issues, and the announcement does not establish that the vulnerabilities are harmless or unlikely to be targeted. Users and administrators should treat the update as a preventive security measure, rather than waiting for evidence of an attack.
The immediate priority is to confirm that Chrome has updated across personal and managed devices. The release’s unusually large count of fixes, combined with six critical ratings, gives organizations a clear reason to track deployment completion. Google has not disclosed active exploitation, and the available release details do not support conclusions about particular attackers or affected organizations. For now, the practical response is straightforward: apply Chrome 158 and ensure the patched browser is in use.