Chrome 155's October Stable Updates: Check Your Browser Version

A browser update is easy to postpone because it interrupts the next tab. Google’s two October Chrome 155 stable-channel notices give users a concrete reason to check: they list critical and high-severity security fixes across the October 13 and October 15 releases. The practical step is simple—check the installed version and restart Chrome if the update is waiting.

What changed in the October releases

Google’s October 13 desktop notice lists Chrome 155.0.8059.79 for Linux and .79/.80 for Windows and Mac, with 37 security fixes. It identifies two critical vulnerabilities, including CVE-2026-110152 in ANGLE and CVE-2026-110149 in the browser. The October 15 notice lists follow-up .84/.85 builds for desktop. The October 13 stable notice is the one that itemizes the 37 fixes and names CVE-2026-110152 and CVE-2026-110149 as critical. ^{[1] [2]}

The release channel matters: stable builds roll out gradually, so a device may not receive the exact same build at the same moment. Google directs desktop users to the About Chrome updater, which checks for the version available to that platform. Restarting completes the update process.

What a severity label tells you—and what it does not

The release notes identify vulnerability severity and fixes. The cited notices do not state that these specific bugs were exploited in the wild. That distinction should be preserved: a critical patch deserves prompt installation even when there is no public claim of active exploitation.

Chromium’s security process explains that vulnerability details may be restricted while fixes are being prepared and distributed, as part of coordinated disclosure. That can mean the initial public information is deliberately limited. It is not a basis for guessing at exploit availability or impact beyond what the release notice says. ^[3]

Check and restart

In Chrome, open the three-dot menu and choose Help → About Google Chrome. Let the browser check for updates, then select Relaunch if prompted. If the device is managed by an organization, follow its update policy and contact IT if Chrome reports that updates are managed.

This small maintenance step is part of keeping a browser secure, alongside using unique passwords, enabling multi-factor authentication, and removing extensions you no longer need. For more security context, read our coverage of software supply-chain defenses and a malicious GitHub Actions dependency incident.

The October notices are a reminder that browser security is an ongoing maintenance task, not a one-time setup. The October 13 release notes listed critical fixes; the October 15 notice records a follow-up stable build. Updating closes known vulnerabilities in the shipped build; it does not guarantee a device is free of every security risk. Use the updater, restart, and rely on Google’s release notes for what each patch actually documents.