Should you update to Chrome 153.0.8010.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 153.0.8010.47 is a security update Google released on 15 Sep 2026 for Mac, Windows and Linux. It fixes 42 security flaws, 3 rated critical and 28 high by Google.[1] None of them is known to be used in attacks.

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

Is Chrome 153.0.8010.47 still safe?

Not any more. The 11 updates since, up to Chrome 157.0.8103.38, fix 1,100 security flaws that Chrome 153.0.8010.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 42 security flaws, 3 rated critical and 28 high by Google.[1] The 31 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-91726CriticalOut of bounds read in WebGL
CVE-2026-91721CriticalUse after free in Internals
CVE-2026-91749CriticalUse after free in Workers
CVE-2026-91724HighUse after free in Input
CVE-2026-91728HighInteger overflow in V8
CVE-2026-91734HighIncorrect authorization in Core
CVE-2026-91727HighIncorrect reference resolution in Extensions
CVE-2026-91743HighRace condition in Core
CVE-2026-91744HighRace condition in PlatformIntegration
CVE-2026-91712HighRace condition in Extensions
CVE-2026-91748HighRace condition in Extensions
CVE-2026-91720HighUninitialized resource in ANGLE
CVE-2026-91731HighType confusion in Compositing
CVE-2026-91747HighUse after free in Skia
CVE-2026-91733HighImproper state validation in Skia
CVE-2026-91741HighType confusion in CacheStorage
CVE-2026-91709HighType confusion in ServiceWorker
CVE-2026-91717HighMissing authorization in Android
CVE-2026-91735HighIncorrect authorization in WebUI
CVE-2026-91708HighRace condition in Network
CVE-2026-91736HighUse after free in DOM
CVE-2026-91740HighUninitialized resource in Skia
CVE-2026-91710HighUse after free in WebAppInstalls
CVE-2026-91718HighUse after free in Core
CVE-2026-91716HighUse after free in Auth
CVE-2026-91746HighInteger overflow in Compositing
CVE-2026-91729HighUse after free in DigitalCredentials
CVE-2026-91737HighUse after free in PDF
CVE-2026-91711HighOut of bounds write in ServiceWorker
CVE-2026-91715HighType confusion in ServiceWorker
and 1 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 153.0.8010.52 or later.

153.0.8010.36 vs 153.0.8010.47

Chrome 153.0.8010.36, released 8 Sep 2026, fixed 230 security flaws, one already used in attacks. Chrome 153.0.8010.47 fixes 42 security flaws and includes the fixes before it, so going straight to 153.0.8010.47 gets you both.

References

  1. ^ Google. “Stable Channel Update for Desktop”, 15 Sep 2026.