Chrome 155.0.8059.79 security update: 37 fixes, seven Criticals

If Chrome is your daily browser at home, this is a mid-train Stable security bump on the 155 line, not another major-version jump. On October 13, 2026, Google pushed a new Stable desktop build with 37 security fixes, including seven Critical items.

This is distinct from the earlier Chrome 155.0.8059.39 package (October 6, 247 fixes) and from the Chrome 156 Early Stable peek. Those notes still matter for context. Today’s target is 155.0.8059.79 (and .80 on Windows/Mac).

What Google shipped

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

• Windows / Mac: 155.0.8059.79 or 155.0.8059.80
• Linux: 155.0.8059.79

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

The Critical items named in that Stable note are:

• CVE-2026-110152: Buffer overflow in ANGLE (Zhenpeng (Leo) Lin at depthfirst)
• CVE-2026-110149: Use after free in Browser (Google)
• CVE-2026-110136: Use after free in PDF (Xinyang Ge)
• CVE-2026-110161: Use after free in Network (Google)
• CVE-2026-110165: Use after free in Core (Google)
• CVE-2026-110148: Use after free in SVG (Xinyang Ge)
• CVE-2026-110151: Use after free in Media (Xinyang Ge)

You do not need the High-severity scavenger hunt after that. Seven Critical bugs in one Stable package is enough reason to install, fully quit, and relaunch.

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

If chrome://version still shows 155.0.8059.39 or .40, you are on the October 6 train. That was a huge first-week-of-155 package. This October 13 bump is a separate security batch on the same major line.

If you somehow still show 154.0.8037.x, read the 155.0.8059.39 note first, then come back here. Do not chase random Chrome 156 installers unless Google already offered Early Stable 156 on your machine (Early Stable guide).

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.79 or .80 (Linux: .79).
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.79 or 155.0.8059.80 (Linux: .79).
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 .79/.80 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.79 when it appears. Google said it would roll out over the next few days after the October 13 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 (or chrome://settings/help), relaunch, and confirm chrome://version shows 155.0.8059.79 or .80 (Linux .79).
• Update Android Chrome from Google Play to 155.0.8059.79 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 seven Critical bugs as “install today,” not “install when I remember on Sunday.”

Don’t

• Do not stop at 155.0.8059.39/.40 because you already “did the Chrome 155 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 wait for exploit details. Google has not said any of these bugs are being exploited, and patching is still the job.

Bottom line

Google’s October 13, 2026 Stable update ships Chrome 155.0.8059.79/.80 (Linux .79) with 37 security fixes, including seven Critical bugs such as the ANGLE buffer overflow (CVE-2026-110152) and Critical use-after-free issues in Browser, PDF, Network, Core, SVG, and Media (official Stable Channel Update). Android Chrome 155.0.8059.79 carries the matching security set (Android note). This sits beyond the earlier 155.0.8059.39 package and is separate from Chrome 156 Early Stable. On your own computer: update, fully quit and relaunch, confirm chrome://version. That is the whole job.

Image: Google Chrome safety page art (google.com/chrome/safety).