Should you update to Chrome 151.0.7922.108?
No: install Chrome 157.0.8103.38 instead. Chrome 151.0.7922.108 is a security update Google released on 6 Aug 2026 for Mac, Windows and Linux. It fixes 41 security flaws, 6 rated critical and 35 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 151.0.7922.137, released 11 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.108, 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.108 still safe?
Not any more. The 19 updates since, up to Chrome 157.0.8103.38, fix 1,764 security flaws that Chrome 151.0.7922.108 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 41 security flaws, 6 rated critical and 35 high by Google.[1] The 41 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-19137 | Critical | Use after free in WebGL |
CVE-2026-19149 | Critical | Use after free in Aura |
CVE-2026-19154 | Critical | Use after free in Skia |
CVE-2026-19157 | Critical | Out of bounds write in ANGLE |
CVE-2026-19170 | Critical | Use after free in WebGL |
CVE-2026-19172 | Critical | Use after free in Views |
CVE-2026-19169 | High | Insufficient validation of untrusted input in Contextual Tasks |
CVE-2026-19168 | High | Inappropriate implementation in V8 |
CVE-2026-19138 | High | Heap buffer overflow in CrashReporting |
CVE-2026-19139 | High | Race in CredentialProvider |
CVE-2026-19140 | High | Use after free in GPU |
CVE-2026-19141 | High | Use after free in Resources |
CVE-2026-19142 | High | Use after free in Views |
CVE-2026-19143 | High | Insufficient validation of untrusted input in WebAPKs |
CVE-2026-19144 | High | Use after free in HTML |
CVE-2026-19145 | High | Use after free in Translate |
CVE-2026-19146 | High | Uninitialized Use in GPU |
CVE-2026-19147 | High | Use after free in Aura |
CVE-2026-19148 | High | Out of bounds write in GPU |
CVE-2026-19150 | High | Inappropriate implementation in V8 |
CVE-2026-19151 | High | Use after free in V8 |
CVE-2026-19152 | High | Inappropriate implementation in Navigation |
CVE-2026-19153 | High | Insufficient validation of untrusted input in Workers |
CVE-2026-19155 | High | Use after free in Payments |
CVE-2026-19156 | High | Heap buffer overflow in Base |
CVE-2026-19158 | High | Use after free in Views |
CVE-2026-19159 | High | Use after free in Views |
CVE-2026-19160 | High | Uninitialized Use in Skia |
CVE-2026-19161 | High | Uninitialized Use in Skia |
CVE-2026-19162 | High | Out of bounds write in V8 |
| and 11 more | ||
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.137 or later.
151.0.7922.75 vs 151.0.7922.108
Chrome 151.0.7922.75, released 4 Aug 2026, fixed 0 security flaws. Chrome 151.0.7922.108 fixes 41 security flaws and includes the fixes before it, so going straight to 151.0.7922.108 gets you both.
- Before: Chrome 151.0.7922.75, 4 Aug 2026, 0 security flaws
- After: Chrome 151.0.7922.137, 11 Aug 2026, 5 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”, 6 Aug 2026.