Should you update to Chrome 155.0.8059.79?

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

It has since been replaced by Chrome 155.0.8059.84, released 15 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.79, 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.79 still safe?

Not any more. The 5 updates since, up to Chrome 157.0.8103.38, fix 649 security flaws that Chrome 155.0.8059.79 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 37 security flaws, 7 rated critical and 29 high by Google.[1] The 36 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-110152CriticalBuffer overflow in ANGLE
CVE-2026-110149CriticalUse after free in Browser
CVE-2026-110136CriticalUse after free in PDF
CVE-2026-110161CriticalUse after free in Network
CVE-2026-110165CriticalUse after free in Core
CVE-2026-110148CriticalUse after free in SVG
CVE-2026-110151CriticalUse after free in Media
CVE-2026-110162HighUse after free in Desktop
CVE-2026-110170HighUse after free in Bindings
CVE-2026-110160HighMissing authorization in ReadingMode
CVE-2026-110143HighUse of uninitialized variable in ThirdParty lmza_sdk
CVE-2026-110146HighInformation leak in Passwords
CVE-2026-110150HighPrivilege elevation in Installer
CVE-2026-110156HighIncorrect reference resolution in Extensions
CVE-2026-110137HighUse after free in WebRTC
CVE-2026-110140HighType confusion in V8
CVE-2026-110158HighUse after free in Passwords
CVE-2026-110145HighUse after free in Passwords
CVE-2026-110159HighIncorrect authorization in Updater
CVE-2026-110144HighIncorrect authorization in Mojo
CVE-2026-110153HighUse after free in Media
CVE-2026-110166HighBuffer overflow in Animation
CVE-2026-110169HighUse after free in V8
CVE-2026-110168HighUse after free in V8
CVE-2026-110139HighUse after free in Media
CVE-2026-110172HighUse after free in Media
CVE-2026-110164HighUse after free in DOM
CVE-2026-110163HighUse after free in DOM
CVE-2026-110141HighObservable discrepancy in Media
CVE-2026-110138HighUse after free in ShapeDetection
and 6 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.84 or later.

155.0.8059.39 vs 155.0.8059.79

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

References

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