Qutzl LLC LogoQutzl

Advertisement

5 min read

Chrome 154.0.8037.92 mid-cycle security update: install, relaunch, verify

Google's September 29, 2026 Stable desktop update ships Chrome 154.0.8037.92/.93 with 32 security fixes, including Critical CVE-2026-102331 in ANGLE. Android 154.0.8037.92 matches. Update, relaunch, confirm chrome://version.

By Michael NarehoodSoftware & Releases

If Google Chrome is your everyday browser on a home PC or Mac, treat this as a “do it now” mid-cycle security bump. You are already supposed to be on the Chrome 154 train. This package moves Stable deeper into 154 with a Critical graphics fix.

On Tuesday, September 29, 2026, Google’s Stable Channel Update for Desktop updated Stable to 154.0.8037.92/.93 for Windows and Mac and 154.0.8037.92 for Linux, rolling out over the coming days and weeks. The same note counts 32 security fixes. The top item is Critical CVE-2026-102331: a buffer overflow in ANGLE.

The same day, Google also shipped Chrome 154.0.8037.92 for Android through Google Play. Android Chrome gets the same security fixes as the matching desktop package unless Google says otherwise.

This article is not the September 22 Stable promotion. That story covered the jump to Chrome 154 as 154.0.8037.57/.58. See our earlier Chrome 154 Stable note. Same habit every time: update, fully quit, relaunch, prove it with chrome://version.

Why this mid-cycle bump matters

A Critical ANGLE buffer overflow is the kind of bug that can matter on ordinary browsing. ANGLE sits under WebGL and related graphics paths. 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.

The September 29 desktop note also lists a long High set covering Mojo, Omnibox, ANGLE, V8, Bluetooth, Dawn, GPU, WebGPU, Views, Passwords, FullScreen, Skia, PictureInPicture, WebGL, WebUI, Media, and more, plus Medium and Low items. You do not need to memorize CVE IDs. You need the new process running.

If chrome://version still shows 154.0.8037.57 or .58 from the September 22 promotion, you are behind this security package. Get to .92 or .93.

Target builds

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

  • Windows / Mac: 154.0.8037.92 or 154.0.8037.93
  • Linux: 154.0.8037.92

From the Android Stable note:

  • Android Chrome: 154.0.8037.92 (Google Play)

Phone Chrome updates through the store. Desktop Chrome does not. Update both if you use both.

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.92 or .93.
  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.92 or 154.0.8037.93 (Linux: .92).
  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.

Android Chrome (Google Play), separately

If you use Chrome on an Android phone or tablet:

  1. Open the Google Play store (or your Play updates list).
  2. Update Chrome to 154.0.8037.92 when it appears. Google said it would roll out over the next few days after the September 29 note.
  3. Open Chrome once after the update so the new build actually launches.

Do not assume a desktop update fixed your phone, or the reverse. iOS Chrome follows the App Store on its own schedule. This desktop and Android pair is the September 29 security train.

Do this / don’t do that

Do

  • Force About Google Chrome, relaunch, and confirm chrome://version shows 154.0.8037.92 or .93.
  • Update Android Chrome from Google Play if that is how you browse on the phone.
  • 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 .92/.93 yet, then check again.

Don’t

  • Do not assume a Windows reboot alone applied this build if chrome://version is still on .57/.58.
  • 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 mid-cycle security package with “I already moved to Chrome 154 last week, so I am done.” The September 22 promotion is not this week’s Critical ANGLE fix.

Bottom line

Google’s September 29, 2026 Stable update ships Chrome 154.0.8037.92/.93 (Linux .92) with 32 security fixes, including Critical CVE-2026-102331 (buffer overflow in ANGLE) (official Stable Channel Update). Android Chrome 154.0.8037.92 carries the matching security set (Android note). This is distinct from the Chrome 154 Stable promotion. 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