Qutzl LLC LogoQutzl

Advertisement

5 min read

Chrome 154 is on Stable: update, then prove it with chrome://version

Google promoted Chrome 154 to desktop Stable on September 22, 2026 with 108 security fixes, including many Critical bugs. iOS Chrome 154.0.8037.55 is also out. Update, relaunch, confirm chrome://version.

By Michael NarehoodSoftware & Releases

If Google Chrome is your everyday browser on a home PC or Mac, treat Tuesday’s Stable promotion as a “do it now” update. This is the big Chrome 154 train, not another mid-cycle bump inside 153.

On Tuesday, September 22, 2026, Google’s Stable Channel Update for Desktop promoted Chrome 154 to Stable for Windows, Mac, and Linux. The build numbers to look for are 154.0.8037.57 on Linux and 154.0.8037.57 or 154.0.8037.58 on Windows and Mac. The same note counts 108 security fixes, including a long list of Critical issues in components such as ANGLE, GPU, ServiceWorker, WebGL, Fullscreen, and related graphics and browser plumbing.

Separately, Google also shipped Chrome Stable 154 for iOS as 154.0.8037.55, described as stability and performance improvements. Phone Chrome updates through the App Store. Desktop Chrome does not. Update both if you use both.

This article is separate from our earlier Chrome 153 Stable promotion, the Chrome 153 Critical mid-cycle security bump, and the CVE-2026-85046 Chrome 152 patch-now story. Same habit every time: update, fully quit, relaunch, prove it with chrome://version.

Why 108 fixes is not a shrug

A major Stable promotion often ships the security backlog from the whole release cycle. You do not need to memorize CVE IDs. You need the new process running.

Google’s September 22 desktop note lists many Critical fixes by name, including buffer overflows and out-of-bounds writes in ANGLE and GPU, use-after-free bugs in ServiceWorker, Fullscreen, WindowDialog, and AdFilter, plus Critical WebGL issues. There is also a long High list covering Extensions, Navigation, V8, PDFium, Bluetooth, HID, and more.

Memory safety bugs in graphics and worker paths are the ones that matter on ordinary browsing. A crafted page or web app is exactly the class of risk browser vendors rush to close. Google still restricts some bug details until more people are patched. That is normal. It is not a reason to wait.

Target builds

From Google’s September 22 Stable Channel Update for Desktop:

  • Windows / Mac: 154.0.8037.57 or 154.0.8037.58
  • Linux: 154.0.8037.57

From the iOS Stable note:

  • iOS Chrome: 154.0.8037.55 (App Store)

If chrome://version still shows 153.x (or an older 154 Canary/Beta build you were testing), you are not on this Stable package yet.

How to update and verify on a home PC or Mac

  1. Open Google Chrome on the computer you actually browse on.
  2. Check for updates:
    • Windows / Linux: Menu (three dots) → Help → About Google Chrome.
    • Mac: Chrome menu → About Google Chrome.
  3. Stay on that page until the download finishes and Chrome offers a relaunch, or until it already shows 154.0.8037.57 or .58.
  4. Relaunch when prompted. Do not click Later and leave old windows open.
  5. If the version still looks old, fully quit Chrome (every window). On Windows, confirm no leftover chrome.exe processes in Task Manager. On Mac, use Chrome → Quit Google Chrome. Then open Chrome again.
  6. Type chrome://version in the address bar and read the first version line. You want 154.0.8037.57 or 154.0.8037.58 (Linux: .57).
  7. Repeat on other computers you use, including a laptop that stays open for days and any shared family PC that still runs Chrome.

Chrome can download an update quietly while you keep reading on the old process. Downloaded is not the same as running. The address-bar check is the proof.

Phone Chrome (App Store), separately

If you use Chrome on an iPhone or iPad:

  1. Open the App Store.
  2. Check your profile / Updates list for Chrome.
  3. Update to 154.0.8037.55 when it appears (Google said it would roll out over the next few hours after the September 22 note).
  4. Open Chrome once after the update so the new build actually launches.

Do not assume a desktop update fixed your phone, or the reverse.

Do this / don’t do that

Do

  • Force About Google Chrome, relaunch, and confirm chrome://version shows 154.0.8037.57 or .58.
  • Update each Chromium browser you actually use (Edge, Brave, and so on) on its own schedule. Updating Chrome does not update them.
  • Give Stable a day to reach you if About Chrome says an update is coming but does not offer .57/.58 yet, then check again.
  • Update iOS Chrome from the App Store if that is how you browse on the phone.

Don’t

  • Do not assume a Windows reboot alone applied this build if chrome://version is still on 153.
  • Do not leave old Chrome windows or background helpers running after an update prompt.
  • Do not skip the version check because the About page looked green.
  • Do not confuse this major 154 promotion with “I already patched Chrome 153 last week, so I am done.”

Bottom line

Google promoted Chrome 154 to desktop Stable on September 22, 2026 as 154.0.8037.57 (Linux) and 154.0.8037.57/.58 (Windows/Mac), with 108 security fixes and many Critical items in ANGLE, GPU, ServiceWorker, WebGL, Fullscreen, and related components (official Stable Channel Update). iOS Chrome 154.0.8037.55 is a separate App Store update (iOS Stable note). On your own computer: update, fully quit and relaunch, confirm chrome://version. That is the whole job.

Image: Google Chrome marketing homepage art (google.com/chrome).

Advertisement