Update Chrome Now: August 2026 Critical Security Fixes

In a roughly 48-hour stretch in the second half of August 2026, Google shipped three critical, sandbox-escaping memory bugs in Chrome and patched them fast. If you use Chrome, the fix is simple: update to at least version 151.0.7922.173 and relaunch the browser. This guide explains what the flaws are, who they affect, and how to confirm you are actually patched rather than just assuming the background updater handled it.

What’s happening#

Google’s Chrome Releases blog posted a Stable channel update on August 18, 2026 that fixed two flaws rated Critical, the highest tier Google assigns. Both are memory-corruption bugs in the browser’s graphics stack: CVE-2026-76034 in WebGL and CVE-2026-76036 in Dawn, the component that implements the WebGPU standard for hardware-accelerated graphics. Two days later, a follow-up update on August 20 fixed a third Critical bug, CVE-2026-76017, a use-after-free in Chromoting (the code behind Chrome Remote Desktop).

The reason these matter more than an ordinary bug is where they live. Chrome runs untrusted web content inside a sandbox that is supposed to keep a malicious page walled off from the rest of your computer. All three flaws sit in processes that can be pushed to run code outside that sandbox, which is why Google labeled them Critical. There is no public report that any of the three was exploited in real attacks, but a critical rating means the fix is worth applying promptly rather than whenever you next happen to restart.

Three Critical memory bugs patched inside roughly two days is a faster cadence than usual, and it is a useful reminder of how browser security actually works now: fixes land continuously in the background, and the only step left to you is restarting to pick them up.

Fix	Component	Bug type	Fixed in	Date
CVE-2026-76034	WebGL	Buffer overflow	151.0.7922.169	Aug 18, 2026
CVE-2026-76036	Dawn (WebGPU)	Buffer overflow	151.0.7922.169	Aug 18, 2026
CVE-2026-76017	Chromoting	Use-after-free	151.0.7922.173	Aug 20, 2026

Because the August 20 build rolls up everything before it, getting to 151.0.7922.173 (or anything newer) closes all three.

Who is affected#

This applies to desktop Chrome on Windows, macOS, and Linux running a version below the fixed builds. WebGL and WebGPU are turned on by default, so there is no special setting that puts you at risk and none that safely leaves you exposed while you wait. The exposure comes from simply loading a page built to trigger the flaw, which is the same reason it pays to be cautious about where links take you in the first place, a habit covered in our guide to spotting a phishing email.

Chrome is not the only browser involved. Microsoft Edge, Brave, Opera, and Vivaldi are all built on the same Chromium engine, so the same graphics-stack code ships inside them. Each vendor issues its own updates on its own schedule, so patching Chrome does not patch Edge, and vice versa. Chrome on Android and iOS updates through the Play Store and App Store rather than the desktop updater, so those follow the usual app-update path.

Browser	Affected?	How it gets the fix
Chrome (desktop)	Yes	Built-in updater, then relaunch
Microsoft Edge	Yes, same engine	Edge’s own update, then restart
Brave / Opera / Vivaldi	Yes, same engine	Each vendor’s own update
Chrome (Android / iOS)	Yes	Play Store / App Store

How to update Chrome and confirm it worked#

Chrome checks for updates on its own, but the download does nothing until you relaunch, and a lot of people keep the browser open for days or weeks. That gap is the whole problem: the patch can be sitting on disk while you are still running the vulnerable build. Forcing the check and relaunching takes under a minute.

Follow the steps Google lists on its own update Google Chrome help page:

Step	What you do	What to look for
1	Click the three-dot More menu at the top right	The dropdown opens
2	Choose Help, then About Google Chrome	The About page opens and checks for updates
3	Let it download if an update is found	A progress line appears
4	Click Relaunch	Chrome restarts and reopens your tabs
5	Reopen the About page	Version reads 151.0.7922.173 or higher

The version string reads as four dot-separated numbers, such as 151.0.7922.173; the part that matters here is the final group, the build number, which needs to be 173 or higher on a Chrome 151 install. If the About page shows no Relaunch button and reports that Chrome is up to date, you are already on the current build. Your open tabs and windows come back after the relaunch; Incognito windows do not reopen, so save anything you need from them first. On a work computer where updates are managed by an administrator, the option may be grayed out, in which case the fix arrives through your IT team’s own rollout.

Update Edge and other Chromium browsers too#

Because Edge shares Chromium’s engine, Microsoft ships the matching graphics-stack fixes in its own updates. Open Edge’s three-dot menu, choose Help and feedback, then About Microsoft Edge. Edge checks for and downloads any update on that screen, then offers a Restart button that finishes the job. Brave, Opera, and Vivaldi work the same way through their own About pages. The pattern is identical everywhere: the update downloads quietly, but nothing is patched until you restart the browser.

Keep the browser patched without thinking about it#

The single habit that keeps you covered is closing and reopening your browser now and then instead of leaving it running for weeks. That one restart is what turns a downloaded update into an installed one, and it costs you nothing but a few reopened tabs. Pair that with the basics that limit the damage when something does slip through: a unique, strong password on every account and phishing-resistant sign-in through passkeys, so a single compromised page cannot cascade into a compromised account.