iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Update Chrome now. Google announced Chrome Stable 155.0.8059.79/.80 for Windows and Mac and 155.0.8059.79 for Linux on October 13, 2026, with 37 security fixes. The release includes critical CVE-2026-110152, a buffer overflow in ANGLE. Install the update from Chrome’s About page, then restart the browser. Microsoft Edge follows a separate release pipeline, so its matching Chromium fixes may arrive later.
What Google released on October 13
Google’s Chrome release notice says, “This update includes 37 security fixes.” The versions differ slightly by operating system:
| Platform | Chrome Stable version |
|---|---|
| Windows | 155.0.8059.79 or 155.0.8059.80 |
| Mac | 155.0.8059.79 or 155.0.8059.80 |
| Linux | 155.0.8059.79 |
Google said the rollout would continue over the coming days and weeks, so some installations may not offer the new build immediately. The 37-fix total applies to this Chrome release; it is not a confirmed count for Edge.
The most serious listed issue
The release entry identifies CVE-2026-110152 as a critical buffer overflow in ANGLE, the graphics translation layer used by Chromium-based browsers. “Critical” is Google’s severity classification for the issue. It does not mean that every Chrome installation has been compromised, nor does the announcement establish that all 37 flaws are being exploited.
#1 Best Overall
How to install Chrome 155
- Open Chrome on Windows, Mac or Linux.
- Select the three-dot menu in the upper-right corner.
- Choose Help, then About Google Chrome.
- Allow Chrome to check for and download the available update. If version 155 is already installed, Chrome will report that it is up to date.
- Select Relaunch when prompted. Save work in open tabs and applications first, because the restart closes the browser window.
After relaunching, return to Help > About Google Chrome and verify that the installed version begins with 155.0.8059. On managed work or school devices, an administrator may control update timing; contact the administrator if the update page reports a policy restriction.
Why Edge may not show the same fixes yet
Chromium is the shared open-source foundation for Chrome and Edge, but Google and Microsoft package, test and distribute their browsers independently. A vulnerability fix can therefore appear in Chrome before it appears in an Edge Stable build. The contemporaneous update report said Edge had not yet shipped the corresponding update at publication time; that status should not be read as proof that Edge is permanently unprotected or that its next build will contain every one of Chrome’s 37 fixes.
Microsoft’s Edge documentation lists Edge Stable 155.0.4283.45, dated October 8, 2026, as the latest major Stable version on the cited release-notes page and provides security updates separately. Microsoft also says, “For the Stable Channel, updates roll out progressively over one or more days.” Its documentation adds that Edge has completed the move to a two-week update cadence. Those statements explain why the version number, release date and patch timing do not line up exactly with Chrome’s.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Edge users should do
- Open Edge and select the three-dot menu.
- Choose Help and feedback, then About Microsoft Edge.
- Let Edge check for updates and install any offered Stable release.
- Select Restart when Edge requests it, then revisit the About page to confirm the new version.
If Edge still shows 155.0.4283.45 and no update is offered, check again later rather than assuming the browser has received Chrome’s patch set. Microsoft’s progressive rollout can make the update available at different times across devices. Organizations using managed Edge should also check their update policies and Microsoft’s security-advisory page for the matching release.
How to judge the urgency
- Chrome: High priority. Install the offered Chrome 155 update and restart, especially because the release lists a critical ANGLE buffer overflow.
- Edge: Update as soon as Microsoft publishes and delivers the corresponding Stable release. Until then, do not claim that Edge contains all 37 Chrome fixes or that it is wholly unprotected.
- Any browser: Keep the operating system, graphics drivers and security software current, and avoid treating a version number alone as evidence that a particular vulnerability is fixed.
What the 37-fix number does—and does not—tell you
The number is a release-level count supplied by Google, not a measure of how many flaws affect every user, how many are remotely exploitable, or how many have known attacks. Individual fixes can carry different severity ratings and affect different browser components. Edge may incorporate overlapping Chromium patches on a different schedule, but only Microsoft’s matching advisory can establish which vulnerabilities and fixes are included in a specific Edge build.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check your browser before continuing sensitive work
On both browsers, the practical check is simple: open the browser’s About page, wait for the update process to finish, and restart when requested. If the browser cannot update, note the exact version and any policy or error message, then use the vendor’s official support or security-update channel. Do not keep a vulnerable browser session open indefinitely just because a rollout has not reached the device; close it and retry after the vendor makes the release available.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
