Should you update to Chrome 156.0.8078.47?

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

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

Is Chrome 156.0.8078.47 still safe?

Not any more. The 3 updates since, up to Chrome 157.0.8103.38, fix 286 security flaws that Chrome 156.0.8078.47 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 353 security flaws, 7 rated critical and 60 high by Google.[1] The 67 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-120931CriticalOut of bounds write in WebGL
CVE-2026-113341CriticalUse after free in Skia
CVE-2026-113279CriticalUse after free in Accessibility
CVE-2026-113072CriticalUse after free in CSS
CVE-2026-113280CriticalUse after free in Paint
CVE-2026-113271CriticalUse after free in Accessibility
CVE-2026-113303CriticalUse after free in WebRTC
CVE-2026-113101HighIncorrect authorization in SiteIsolation
CVE-2026-113097HighMissing authorization in FileSystem
CVE-2026-113098HighType confusion in CacheStorage
CVE-2026-113242HighUninitialized resource in ANGLE
CVE-2026-113058HighMissing authorization in WebUI
CVE-2026-113082HighInteger overflow in ANGLE
CVE-2026-113119HighImproper certificate validation in Network
CVE-2026-113092HighMissing authorization in Passwords
CVE-2026-113134HighOut of bounds read in ANGLE
CVE-2026-113222HighMissing authorization in V8
CVE-2026-113339HighUse after free in SVG
CVE-2026-113317HighUse after free in Accessibility
CVE-2026-113193HighType confusion in V8
CVE-2026-113117HighOut of bounds read in ANGLE
CVE-2026-120930HighIncorrect authorization in Blink
CVE-2026-113188HighUninitialized resource in GPU
CVE-2026-113104HighUse after free in Frames
CVE-2026-113322HighUninitialized resource in Dawn
CVE-2026-113163HighBuffer overflow in WebGL
CVE-2026-113253HighIncorrect authorization in Canvas
CVE-2026-113298HighUI misrepresentation in Transactions Platform
CVE-2026-113315HighUninitialized resource in ANGLE
CVE-2026-113236HighImproper input validation in Navigation
and 37 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 156.0.8078.73 or later.

155.0.8059.84 vs 156.0.8078.47

Chrome 155.0.8059.84, released 15 Oct 2026, fixed 10 security flaws. Chrome 156.0.8078.47 fixes 353 security flaws and includes the fixes before it, so going straight to 156.0.8078.47 gets you both.

References

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