Should you update to Chrome 155.0.8059.39?

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 155.0.8059.39 is a security update Google released on 6 Oct 2026 for Mac, Windows and Linux. It fixes 247 security flaws, 4 rated critical and 53 high by Google.[1] None of them is known to be used in attacks.

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

Is Chrome 155.0.8059.39 still safe?

Not any more. The 6 updates since, up to Chrome 157.0.8103.38, fix 686 security flaws that Chrome 155.0.8059.39 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 247 security flaws, 4 rated critical and 53 high by Google.[1] The 57 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-106382CriticalUse after free in Chromecast
CVE-2026-106197CriticalUse after free in Browser
CVE-2026-106358CriticalUse after free in Navigation
CVE-2026-106347CriticalUse after free in Track
CVE-2026-102322HighIncorrect Authorization in SiteIsolation
CVE-2026-106245HighUninitialized resource in ANGLE
CVE-2026-106327HighIncorrect authorization in Core
CVE-2026-106366HighIncomplete cleanup in CustomTabs
CVE-2026-106258HighUninitialized resource in ANGLE
CVE-2026-106376HighUninitialized resource in ANGLE
CVE-2026-106308HighIncorrect reference resolution in Autofill
CVE-2026-106215HighUninitialized resource in ANGLE
CVE-2026-106369HighMissing authorization in Translate
CVE-2026-106293HighType confusion in ANGLE
CVE-2026-106377HighRace condition in Fonts
CVE-2026-106412HighRace condition in Core
CVE-2026-106243HighIncomplete cleanup in Proxy Auth
CVE-2026-106214HighInformation leak in Proxy
CVE-2026-106364HighIncorrect authorization in Omnibox
CVE-2026-106239HighInteger overflow in WebGL
CVE-2026-106426HighRace condition in Fonts
CVE-2026-106419HighUse after free in ANGLE
CVE-2026-106396HighImproper input validation in Omnibox
CVE-2026-106323HighMissing authorization in Chrome for iOS
CVE-2026-106231HighUninitialized resource in Dawn
CVE-2026-106202HighUninitialized resource in ANGLE
CVE-2026-106273HighUninitialized resource in Video
CVE-2026-106203HighIncomplete cleanup in Autofill
CVE-2026-106332HighInteger overflow in Compositing
CVE-2026-106281HighUse after free in Tint
and 27 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 155.0.8059.79 or later.

154.0.8037.97 vs 155.0.8059.39

Chrome 154.0.8037.97, released 2 Oct 2026, fixed 11 security flaws. Chrome 155.0.8059.39 fixes 247 security flaws and includes the fixes before it, so going straight to 155.0.8059.39 gets you both.

References

  1. ^ Google. “Stable Channel Update for Desktop”, 6 Oct 2026.