Should you update to Chrome 153.0.8010.36?

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.36 is a security update Google released on 8 Sep 2026 for Mac, Windows and Linux. It fixes 230 security flaws, 5 rated critical and 41 high by Google.[1] One of them is already being used in attacks.

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

Not any more. The 12 updates since, up to Chrome 157.0.8103.38, fix 1,142 security flaws that Chrome 153.0.8010.36 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 230 security flaws, 5 rated critical and 41 high by Google.[1] The 46 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-87464CriticalUse after free in WebGL
CVE-2026-87488CriticalUse after free in WebGL
CVE-2026-87438CriticalOut of bounds write in WebGL
CVE-2026-87527CriticalBuffer overflow in WebGL
CVE-2026-87628CriticalUse after free in Cast
CVE-2026-87512HighUse after free in ANGLE
CVE-2026-87585HighDouble free in PDFium
CVE-2026-87444HighMemory corruption in Codecs
CVE-2026-87447HighIncorrect authorization in Network
CVE-2026-87440HighOut of bounds read in Media
CVE-2026-87633HighUse after free in Views
CVE-2026-87525HighOut of bounds read in Chromoting
CVE-2026-87578HighUse after free in Receiver
CVE-2026-87517HighRace condition in Mobile
CVE-2026-87524HighUse after free in Core
CVE-2026-87569HighMissing authorization in Views
CVE-2026-87554HighRace condition in Chromoting
CVE-2026-87467HighRace condition in Updater
CVE-2026-87492HighIncorrect authorization in DevTools
CVE-2026-87520HighUse after free in Dawn
CVE-2026-87514HighUse after free in Views
CVE-2026-87650HighOut of bounds read in WebGL
CVE-2026-87596HighOut of bounds read in ANGLE
CVE-2026-87654HighBuffer overflow in ANGLE
CVE-2026-87604HighOut of bounds read in ANGLE
CVE-2026-87621HighOut of bounds write in ANGLE
CVE-2026-87647HighUninitialized resource in GPU
CVE-2026-87646HighUse after free in Web Authentication
CVE-2026-87500HighImproper validation of array index in ANGLE
CVE-2026-87572HighInjection in DevTools
and 16 more

Used in attacks

This fix closes a flaw that attackers were already using before the update came out, either on CISA’s list of flaws being used in attacks or in Google’s own words.[2]

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.47 or later.

152.0.7977.82 vs 153.0.8010.36

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

References

  1. ^ Google. “Stable Channel Update for Desktop”, 8 Sep 2026.
  2. ^ Cybersecurity and Infrastructure Security Agency. “Known Exploited Vulnerabilities Catalog”.