Should you update to Chrome 151.0.7922.169?
No: install Chrome 157.0.8103.38 instead. Chrome 151.0.7922.169 is a security update Google released on 18 Aug 2026 for Mac, Windows and Linux. It fixes 15 security flaws, 2 rated critical and 13 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 151.0.7922.173, released 20 Aug 2026, which includes all of its fixes. If you’re on an older version, install that instead.
Should you update?
No: install Chrome 157.0.8103.38 instead. Chrome 157.0.8103.38 came out on 3 Nov 2026 and includes every fix in Chrome 151.0.7922.169, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 151.0.7922.169 still safe?
Not any more. The 17 updates since, up to Chrome 157.0.8103.38, fix 1,744 security flaws that Chrome 151.0.7922.169 doesn’t, and each became public the day its fix shipped. Installing it is safe: get it only from Chrome’s own About page (chrome://settings/help), never from a link in an email, text or pop-up.
What it fixes
Google lists 15 security flaws, 2 rated critical and 13 high by Google.[1] The 15 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-76034 | Critical | Buffer overflow in WebGL |
CVE-2026-76036 | Critical | Buffer overflow in Dawn |
CVE-2026-76033 | High | Inappropriate implementation in CORS |
CVE-2026-76037 | High | Link following in CredentialProvider |
CVE-2026-76044 | High | Race condition in USB |
CVE-2026-76039 | High | Incorrect reference resolution in Core |
CVE-2026-76040 | High | Use after free in Browser |
CVE-2026-76035 | High | Inappropriate implementation in Media |
CVE-2026-76042 | High | Use of uninitialized resource in GPU |
CVE-2026-76046 | High | Buffer overflow in ANGLE |
CVE-2026-76043 | High | Incorrect calculation in V8 |
CVE-2026-76041 | High | Information leak in Skia |
CVE-2026-76047 | High | Type confusion in V8 |
CVE-2026-76038 | High | Type confusion in V8 |
CVE-2026-76045 | High | Use after free in WebGL |
How to update, and how long it takes
A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.
- Open Chrome’s About page.Type chrome://settings/help in the address bar, or open the ⋮ menu → Help → About Google Chrome. Chrome checks and downloads the update.
- Click Relaunch.Chrome reopens your tabs. Until you relaunch, the old, unfixed version keeps running.
- Do the same in every Chromium browser.Edge, Brave, Opera and Vivaldi are built on the same code and get the same fixes a few days later.
To check it worked: chrome://settings/help shows the version, and says “Chrome is up to date” when it is. It should say 151.0.7922.173 or later.
151.0.7922.137 vs 151.0.7922.169
Chrome 151.0.7922.137, released 11 Aug 2026, fixed 5 security flaws. Chrome 151.0.7922.169 fixes 15 security flaws and includes the fixes before it, so going straight to 151.0.7922.169 gets you both.
- Before: Chrome 151.0.7922.137, 11 Aug 2026, 5 security flaws
- After: Chrome 151.0.7922.173, 20 Aug 2026, 7 security flaws
- Chrome updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Google. “Stable Channel Update for Desktop”, 18 Aug 2026.