Chrome 155.0.8059.84 security update: Critical prerender fix

If Chrome is the browser you actually use at home, check the version again. On Thursday, October 15, 2026, Google pushed another Stable security bump on the 155 line: 155.0.8059.84 (and .85 on Windows and Mac).

This is not the October 13 package. Our earlier Chrome 155.0.8059.79 note still mattered last week. It is not today’s target. If chrome://version still shows .79, .80, or anything older on 155, move to .84 / .85.

What Google shipped

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

• Windows / Mac: 155.0.8059.84 or 155.0.8059.85
• Linux: 155.0.8059.84

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

Named items from that Stable note:

• Critical CVE-2026-110922: Use after free in Prerender (Xinyang Ge)
• High CVE-2026-110913: Memory corruption in DOM (Xinyang Ge of Anthropic, assisted by Claude)
• High CVE-2026-110919: Use after free in V8 (Xinyang Ge)
• High CVE-2026-110918: Memory corruption in Core (Google)
• High CVE-2026-110917: Memory corruption in SVG (C0rk1)
• High CVE-2026-110921: Use after free in V8 (Xinyang Ge)
• High CVE-2026-110920: Memory corruption in V8 (Xinyang Ge)
• Plus three Medium items in Desktop, Compositing, and Workers

You do not need a full CVE scavenger hunt. One Critical and six Highs in a mid-train Stable package is enough reason to install, fully quit, and relaunch.

The same day, Google released Chrome 155.0.8059.84 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 155.0.8059.79 is not enough anymore

If you already “did the Chrome 155 update” after October 13, good. That got you onto .79 / .80. It does not include this October 15 security set.

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, or open chrome://settings/help.
   • Mac: Chrome menu → About Google Chrome, or open chrome://settings/help.
3. Stay on that page until the download finishes and Chrome offers a relaunch, or until it already shows 155.0.8059.84 or .85 (Linux: .84).
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.84 or 155.0.8059.85 (Linux: .84).
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 .84/.85 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.84 when it appears. Google said it would roll out over the next few days after the October 15 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 Chrome, relaunch, and confirm chrome://version shows 155.0.8059.84 or .85.
• Treat a Critical prerender use-after-free in Stable as “install today,” not “install when I remember on Sunday.”
• Update Edge, Firefox, Brave, and Safari on their own pages if you use them. Updating Chrome does not update them.
• Fully quit leftover Chrome processes after an update prompt.

Don’t

• Do not stop at 155.0.8059.79 because you already “did the Chrome 155 update.”
• Do not assume a Windows reboot alone applied .84 if chrome://version still shows .79.
• Do not wait for exploit details. Google has not said any of these bugs are being exploited, and patching is still the job.
• Do not download random “Chrome offline installer” packs from third-party sites. Use Chrome’s own About page or Google’s download links.

Bottom line

Google’s October 15, 2026 Stable update ships Chrome 155.0.8059.84/.85 with 10 security fixes, including Critical CVE-2026-110922 (Stable note). Android is 155.0.8059.84 (Android note). This sits beyond the earlier 155.0.8059.79 package. On your own computer: open About Google Chrome, install, fully quit and relaunch, confirm chrome://version. That is the whole job.

Image: Google Chrome browser features marketing art (google.com/chrome/browser-features).