4 min read

Chrome 155.0.8059.39 security update: 247 fixes, four Criticals

Google's October 6, 2026 Stable update ships Chrome 155.0.8059.39/.40 with 247 security fixes, including four Critical use-after-free bugs. Android is 155.0.8059.39. Update, relaunch, confirm chrome://version.

If Chrome is your daily browser at home, this is a new major Stable train, not another 154.x bump. On October 6, 2026, Google moved Stable to Chrome 155 with a very large security package.

This follows our recent Chrome 154.0.8037.97 and Chrome 154.0.8037.92 notes. Those builds mattered last week. They are not today’s target.

What Google shipped

Google’s Stable Channel Update for Desktop (Tuesday, October 6, 2026) updated Stable to:

  • Windows / Mac: 155.0.8059.39 or 155.0.8059.40
  • Linux: 155.0.8059.39

The same note says the rollout takes days or weeks, and that the update includes 247 security fixes.

The Critical items named in that Stable note are:

  • CVE-2026-106382: use after free in Chromecast (Google)
  • CVE-2026-106197: use after free in Browser (Xinyang Ge)
  • CVE-2026-106358: use after free in Navigation (Xinyang Ge / Anthropic, assisted by Claude)
  • CVE-2026-106347: use after free in Track (Xinyang Ge / Anthropic, assisted by Claude)

You do not need the rest of the CVE scavenger hunt. Four Critical use-after-free bugs in one Stable package is enough reason to install, fully quit, and relaunch.

The same day, Google released Chrome 155.0.8059.39 for Android through Google Play. Android Stable notes say Android gets the same security fixes as the matching desktop package unless Google says otherwise.

Why 154.x is not enough anymore

If chrome://version still shows 154.0.8037.x, you are on last week’s major train. Chrome 155 is the new Stable line. The Critical WebGL fix from October 1 mattered. This package is a separate jump with a much larger security batch.

Same habit every time:

  1. Update
  2. Fully quit and relaunch
  3. Prove it with chrome://version

Downloaded is not running. The address bar is the receipt.

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 155.0.8059.39 or .40 (Linux: .39).
  4. Relaunch when prompted. Do not click Later and leave old windows open for hours.
  5. If the version still looks old, fully quit Chrome (every window). On Windows, confirm no leftover chrome.exe in Task Manager. On Mac, use Chrome → Quit Google Chrome. Open Chrome again.
  6. Type chrome://version in the address bar. You want 155.0.8059.39 or 155.0.8059.40 (Linux: .39).
  7. Repeat on other machines you use, including the laptop that sleeps with Chrome still open and any shared family PC.

If About Chrome says an update is coming but does not offer 155 yet, give Stable a day, then check again. Google stages these.

Android Chrome (Google Play), separately

If you browse in Chrome on an Android phone or tablet:

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

A desktop update does not patch your phone. An Android update does not patch your PC. iOS Chrome follows the App Store on its own schedule.

Do this / don’t do that

Do

  • Force About Google Chrome, relaunch, and confirm chrome://version shows 155.0.8059.39 or .40 (Linux .39).
  • Update Android Chrome from Google Play to 155.0.8059.39 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.
  • Treat four Critical use-after-free bugs as “install today,” not “install when I remember on Sunday.”

Don’t

  • Do not stop at 154.0.8037.97/.98 because you already “did the Chrome 154 update.”
  • 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 for a second.
  • Do not invent exploit details for the Critical items. Patching is the job.

Bottom line

Google’s October 6, 2026 Stable update ships Chrome 155.0.8059.39/.40 (Linux .39) with 247 security fixes, including four Critical use-after-free bugs (official Stable Channel Update). Android Chrome 155.0.8059.39 carries the matching security set (Android note). This is beyond the earlier 154.0.8037.97 package. 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