Should you update to Chrome 152.0.7977.64?

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 152.0.7977.64 is a security update Google released on 25 Aug 2026 for Mac, Windows and Linux. It fixes 327 security flaws, 10 rated critical and 61 high by Google.[1] None of them is known to be used in attacks.

It has since been replaced by Chrome 152.0.7977.75, released 1 Sep 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 152.0.7977.64, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.

Is Chrome 152.0.7977.64 still safe?

Not any more. The 15 updates since, up to Chrome 157.0.8103.38, fix 1,410 security flaws that Chrome 152.0.7977.64 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 327 security flaws, 10 rated critical and 61 high by Google.[1] The 71 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-79282CriticalUse after free in ANGLE
CVE-2026-79290CriticalUse after free in Aura
CVE-2026-79054CriticalUse after free in Chromecast
CVE-2026-79121CriticalImproper input validation in Chromecast
CVE-2026-79224CriticalUse after free in Chromecast
CVE-2026-79052CriticalUse after free in Aura
CVE-2026-79150CriticalUse after free in Views
CVE-2026-78935CriticalUse of uninitialized variable in Mobile
CVE-2026-79012CriticalUse after free in Safebrowsing
CVE-2026-79200CriticalUse after free in Aura
CVE-2026-78989HighOut of bounds read in ANGLE
CVE-2026-79069HighMemory corruption in Tint
CVE-2026-79175HighType confusion in Accessibility
CVE-2026-79218HighIncorrect authorization in Sandbox
CVE-2026-79195HighUse after free in Script
CVE-2026-78939HighUse after free in Chromecast
CVE-2026-79194HighUse after free in Chromoting
CVE-2026-79247HighUse after free in Chromoting
CVE-2026-79219HighUse after free in Bluetooth
CVE-2026-79047HighUse after free in Views
CVE-2026-79292HighInteger overflow in Chromecast
CVE-2026-78986HighUninitialized resource in GPU
CVE-2026-79039HighUse after free in Mobile
CVE-2026-78934HighRace condition in ReadAloud
CVE-2026-79011HighUI misrepresentation in Browser
CVE-2026-78911HighIncorrect authorization in USB
CVE-2026-79257HighUse after free in Views
CVE-2026-79202HighUse after free in Chromecast
CVE-2026-79212HighMissing authorization in Passwords
CVE-2026-79183HighUse after free in Accessibility
and 41 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 152.0.7977.75 or later.

151.0.7922.173 vs 152.0.7977.64

Chrome 151.0.7922.173, released 20 Aug 2026, fixed 7 security flaws. Chrome 152.0.7977.64 fixes 327 security flaws and includes the fixes before it, so going straight to 152.0.7977.64 gets you both.

References

  1. ^ Google. “Stable Channel Update for Desktop”, 25 Aug 2026.