Should you update to Chrome 151.0.7922.71?

From Chrome updates, in the HARD wiki · Updated
This article is about one Chrome release. For the latest version, see Chrome updates.

No: install Chrome 157.0.8103.38 instead. Chrome 151.0.7922.71 is a security update Google released on 29 Jul 2026 for Mac, Windows and Linux. It fixes 371 security flaws, 7 rated critical and 71 high by Google.[1] None of them is known to be used in attacks.

It has since been replaced by Chrome 151.0.7922.75, released 4 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.71, 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.71 still safe?

Not any more. The 21 updates since, up to Chrome 157.0.8103.38, fix 1,805 security flaws that Chrome 151.0.7922.71 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 371 security flaws, 7 rated critical and 71 high by Google.[1] The 78 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-17650CriticalUse after free in Compositing
CVE-2026-17651CriticalInsufficient validation of untrusted input in Dawn
CVE-2026-17652CriticalUse after free in Views
CVE-2026-17653CriticalUse after free in Skia
CVE-2026-17654CriticalRace in Updater
CVE-2026-17655CriticalInsufficient validation of untrusted input in ANGLE
CVE-2026-17656CriticalUse after free in Ozone
CVE-2026-17657HighUse after free in Navigation
CVE-2026-17658HighUse after free in V8
CVE-2026-17659HighInappropriate implementation in SiteIsolation
CVE-2026-17660HighInsufficient validation of untrusted input in Network
CVE-2026-17661HighUse after free in Loader
CVE-2026-17662HighInsufficient policy enforcement in Prefetch
CVE-2026-17663HighInsufficient validation of untrusted input in GPU
CVE-2026-17664HighInsufficient validation of untrusted input in Loader
CVE-2026-17665HighUse after free in V8
CVE-2026-17666HighCryptographic Flaw in Enterprise
CVE-2026-17667HighUninitialized Use in ANGLE
CVE-2026-17668HighUninitialized Use in ANGLE
CVE-2026-17669HighInappropriate implementation in Chrome for iOS
CVE-2026-17670HighUse after free in Views
CVE-2026-17671HighInsufficient validation of untrusted input in ANGLE
CVE-2026-17672HighInsufficient validation of untrusted input in Chromecast
CVE-2026-17673HighInteger overflow in QUIC
CVE-2026-17674HighInappropriate implementation in HTML
CVE-2026-17675HighOut of bounds write in ANGLE
CVE-2026-17676HighInappropriate implementation in ANGLE
CVE-2026-17677HighInappropriate implementation in ANGLE
CVE-2026-17678HighOut of bounds read in ANGLE
CVE-2026-17679HighInsufficient validation of untrusted input in Print Preview
and 48 more

How to update, and how long it takes

A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.

  1. 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.
  2. Click Relaunch.Chrome reopens your tabs. Until you relaunch, the old, unfixed version keeps running.
  3. 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.75 or later.

150.0.7871.186 vs 151.0.7922.71

Chrome 150.0.7871.186, released 23 Jul 2026, fixed 4 security flaws. Chrome 151.0.7922.71 fixes 371 security flaws and includes the fixes before it, so going straight to 151.0.7922.71 gets you both.

References

  1. ^ Google. “Stable Channel Update for Desktop”, 29 Jul 2026.