1-minute read
What a defender needs to know
Google’s August 11 Chrome 151 Stable update fixes five high-severity use-after-free flaws across V8, TabStrip, Extensions, HTML, and Blink. The fixed builds are 151.0.7922.137/.138 for Windows and macOS and 151.0.7922.137 for Linux. Google does not report exploitation, victims, or a public proof of concept, and the staged rollout makes the running browser build the necessary check.
Inventory the running Chrome version on every managed desktop endpoint. Force the normal update and browser-restart workflow where the reported build is older than 151.0.7922.137, then query the fleet again. Any later Chrome release supersedes the Chrome 151 fixed line and also satisfies the check.
The expected result is no active Windows, macOS, or Linux endpoint below 151.0.7922.137 after the deployment window. Track devices that cannot update as explicit exceptions and restrict their browser use from untrusted sites and extensions. Check the browser’s reported running build to confirm that the deployed fix is active.