Should you update to Chrome 154.0.8037.57?

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

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

Is Chrome 154.0.8037.57 still safe?

Not any more. The 9 updates since, up to Chrome 157.0.8103.38, fix 976 security flaws that Chrome 154.0.8037.57 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 108 security flaws, 11 rated critical and 25 high by Google.[1] The 36 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-95350CriticalBuffer overflow in ANGLE
CVE-2026-95357CriticalOut of bounds write in GPU
CVE-2026-95339CriticalUse after free in ServiceWorker
CVE-2026-95281CriticalBuffer overflow in ANGLE
CVE-2026-95313CriticalUse after free in Fullscreen
CVE-2026-95349CriticalBuffer overflow in WebGL
CVE-2026-95284CriticalBuffer overflow in ANGLE
CVE-2026-95322CriticalOut of bounds write in GPU
CVE-2026-95329CriticalOut of bounds write in WebGL
CVE-2026-95356CriticalUse after free in WindowDialog
CVE-2026-95310CriticalUse after free in AdFilter
CVE-2026-95301HighMissing authorization in Extensions
CVE-2026-95291HighUI misrepresentation in SecurityIndicators
CVE-2026-95355HighIncorrect authorization in Navigation
CVE-2026-95315HighUse after free in Aura
CVE-2026-95298HighUse after free in Browser
CVE-2026-95372HighUse after free in Chromecast
CVE-2026-95324HighUninitialized resource in GPU
CVE-2026-95283HighBuffer overflow in Tint
CVE-2026-95293HighUninitialized resource in GPU
CVE-2026-95274HighImproper output encoding in DevTools
CVE-2026-95282HighUse after free in Platform
CVE-2026-95373HighUse after free in DevTools
CVE-2026-95277HighUse after free in Views
CVE-2026-95348HighUse after free in Bluetooth
CVE-2026-95335HighUse after free in HID
CVE-2026-95338HighUse after free in PDFium
CVE-2026-95318HighBuffer overflow in Video
CVE-2026-95286HighType confusion in Bindings
CVE-2026-95365HighType confusion in IndexedDB
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 154.0.8037.92 or later.

153.0.8010.52 vs 154.0.8037.57

Chrome 153.0.8010.52, released 17 Sep 2026, fixed 16 security flaws. Chrome 154.0.8037.57 fixes 108 security flaws and includes the fixes before it, so going straight to 154.0.8037.57 gets you both.

References

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