Google Chrome 152.0.7977.82 Fixes 12 Security Vulnerabilities

What's in this update

Google's release notes list 12 security fixes for this build. Details are published progressively on the Chrome Security Page, and Google notes that access to bug specifics and links may remain restricted until a majority of users have updated, or until a fix is available for any affected third-party library that other projects also depend on. Two issues are called out by name in the current notes: CVE-2026-85046, a High-severity type confusion in V8 (Chrome's JavaScript engine) reported by Salvatore Gulizia on 2026-08-04 with a $1,000 reward, and CVE-2026-85052, a High-severity out-of-bounds read in Chrome's crash reporting component.

Why it matters for your stack

V8 is the engine that executes JavaScript in every page Chrome loads, so type confusion bugs there are a common route to memory corruption and potential remote code execution if left unpatched. An out-of-bounds read in the crash reporting path is lower-exposure but still worth closing, since crash handlers can be reachable during otherwise-sandboxed failures. Given that this build carries a dozen fixes in total and at least two rated High, organizations managing fleets of desktop browsers should treat this as a routine but non-optional security update.

How to update

Chrome updates itself automatically in the background on most systems; users can force the check by opening Settings > About Chrome, which will download and apply the new version and prompt for a relaunch. Enterprises managing Chrome via policy or a managed deployment should confirm the update is being pushed through their standard channel, since Google states the rollout will be staged over the next days to weeks rather than delivered to everyone at once.