GOOGLE rolled out Chrome 151 on June 30, addressing 382 security flaws that affect the browser on Windows, macOS and Linux, with 15 of the issues classified as critical and another 67 as high severity, according to the company’s stable channel release blog.
The majority of the patched bugs are use‑after‑free and out‑of‑bounds errors that reside mainly in the renderer process, meaning a malicious web page could trigger remote code execution if exploited, though Google said there have been no reports of active exploitation in the wild for these specific vulnerabilities.
SecurityWeek highlighted that the update continues a recent surge in vulnerability discoveries driven by internal AI‑assisted fuzzing, noting that most of the flaws were uncovered by Google’s own security teams in its coverage.
SecurityOnline urged administrators to ensure users update to version 150.0.7871.46 (or .47 for Windows and macOS) as soon as possible, pointing out that the update is available through the browser’s built‑in update mechanism and can be forced via enterprise policy in its advisory.
Defenders should verify that auto‑update is enabled across all endpoints, review version numbers to confirm the patch has been applied, and consider enforcing site isolation to limit the impact of any renderer‑level flaw that might slip through.
Monitoring browser logs for unexpected renderer crashes or spikes in memory usage can help catch attempted exploitation, while maintaining up‑to‑date threat intelligence feeds will ensure rapid response to any future Chrome‑related advisories.