Chrome 153 is on Stable: update your browser, then check the version

If you browse the web in Google Chrome on your own computer, take a few minutes today and move onto Chrome 153. This is not the same story as the mid-cycle Chrome 152 zero-day patch from last week. Google just promoted a whole new Stable major release, and the security bundle that comes with it is large.

On Tuesday, September 8, 2026, Google’s Stable Channel Update for Desktop announced Chrome 153.0.8010.36 for Linux and 153.0.8010.36/.37 for Windows and Mac. The note says the rollout will continue over the coming days and weeks. The same post counts 230 security fixes in this update.

Why this update matters on a normal PC

A major Stable promotion is when Google finishes a release train and starts shipping it to everyday desktop users. Feature blogs will cover what is new in Chrome 153. Your job is simpler: get onto a build that includes that security work, then prove it with a version check.

Chrome can download an update quietly while you keep reading tabs on the old process. Downloaded is not the same as running. Until you fully quit and relaunch, chrome://version can still show an older line even though an update sat ready in the background.

This post is about the September 8 Stable promotion. It is separate from the earlier CVE-2026-85046 Chrome 152 patch-now note. That piece was a same-day High severity V8 fix with an exploit already in the wild. This one is the next major Stable train, with a much bigger security list.

What Google shipped (versions and a few High CVEs)

Target builds from the official Stable note:

Linux: 153.0.8010.36
Windows / Mac: 153.0.8010.36 or 153.0.8010.37

Google lists many Critical and High issues in that post. You do not need the full catalog to decide whether to update. A few High severity examples named in the Stable advisory:

CVE-2026-87512: Use after free in ANGLE
CVE-2026-87585: Double free in PDFium
CVE-2026-87587: Use after free in V8
CVE-2026-87564: Type confusion in V8

The same advisory also lists Critical WebGL issues such as CVE-2026-87464. Severity labels and short descriptions come from Google’s Chrome Releases post linked above. Prefer that page over third-party summaries when you want the official wording.

Practically: a crafted page, ad, PDF, or web app can hit browser engine bugs while you do ordinary browsing. Updating Chrome closes a large batch of those paths at once.

Update Chrome on Windows, Mac, or Linux

Open Google Chrome on the computer you actually use for the web.
Check for updates.
- Windows / Linux: Menu (three dots) → Help → About Google Chrome.
- Mac: Chrome menu → About Google Chrome.
Let the download finish. Stay on the About page until Chrome says it is ready to relaunch, or until it already shows 153.0.8010.x.
Relaunch when prompted. Do not click Later and walk away with old windows still open.
Fully quit if the version still looks old. On Windows, use Exit from the Chrome menu or close every Chrome window, then confirm in Task Manager that no chrome.exe processes remain. On Mac, use Chrome → Quit Google Chrome. On Linux, quit the app the way you normally do, then start it again.
Verify with chrome://version. Type that into the address bar and read the first version line. You want 153.0.8010.36 or 153.0.8010.37 (Linux: .36).
Repeat on other computers you use, including a laptop that stays open for days and any shared family PC that still runs Chrome.

If About Google Chrome says an update is coming but will not offer 153 yet, wait for your Stable roll to reach you, then force the check again. Google stages Stable over days and weeks.

Do not stop at “it said updated”

Do not assume a Windows reboot alone applied Chrome 153 if chrome://version is still on 152.x or earlier.
Do not leave old Chrome windows or background helpers running after an update prompt. Those keep the old build alive.
Do not skip the address-bar check because the About page looked green. chrome://version is the proof.
Do not assume updating Chrome also updated Microsoft Edge, Brave, or another Chromium browser. Those ship their own builds. Update each one you use.

A note on automatic updates

Chrome is good at downloading updates in the background. That habit still helps. After a major Stable promotion with this many security fixes, take the extra minute: force About Google Chrome, fully quit, relaunch, and read chrome://version. Then go back to your tabs.

If you only use Chrome on a phone, this desktop Stable note is not your checklist. Phone Chrome follows its own store or package updates. This article is for the computer browser on your desk or lap.

Bottom line

Chrome 153.0.8010.36/.37 is on desktop Stable as of September 8, 2026, with 230 security fixes in Google’s Stable Channel Update for Desktop. Update Chrome on your own PC or Mac, fully quit and relaunch so the new process actually runs, and confirm chrome://version shows 153.0.8010.x. That is the whole job.