Chrome 156 Gets a Second Security Update With 21 Fixes

Share

Google has released a second Chrome 156 security update in about a week, this time with 21 fixes, and one of them is rated Critical. According to Google’s Stable Channel update note from October 29, the Stable and Extended Stable channels are moving to 156.0.8078.79/.80 on Windows and Mac and 156.0.8078.79 on Linux, rolling out over the coming days and weeks. Chrome for Android got 156.0.8078.79 the same day.

Key Takeaways: Chrome 156 patch 2
21 fixes: 1 Critical, 19 High and 1 Medium security bug, all patched in one update.
Version to look for: 156.0.8078.79 or later on Windows, Mac, Linux and Android.
Second patch in a week: it follows the 52-fix update from October 27, so if you installed that one, you still need this one.
No attacks mentioned: Google’s note does not say any of these bugs are being used in real attacks.
Chromebooks: a ChromeOS update landed on October 28, but its release note does not list any of these 21 fixes.

1. What this update fixes

Another round: on October 27 Google shipped a Chrome 156 security update with 52 fixes, four of them Critical. Two days later it followed up with this smaller batch. There are no new features here, only security fixes.

The Critical bug: CVE-2026-76024 is a memory corruption bug in MediaStream, the part of Chrome that handles camera and microphone streams for things like video calls. Critical is Google’s top rating, used for the most serious bugs, the kind an attacker could use through a bad web page. Security researcher Xinyang Ge reported it on October 21.

Part of ChromeFixesSeverity
MediaStream (camera and mic streams)1Critical
FileSystem43 High 1 Medium
CacheStorage2High
Skia graphics2High
Quota (site storage limits)2High
V8 JavaScript engine1High
Autofill, Network, Input, Frames, GarbageCollection, Dawn, DOM, Editing and Blink1 each (9)High

Mostly memory bugs: most of the 21 are use after free, memory corruption or input validation problems. These are the kinds of bugs attackers look for, because they can sometimes be used to run their own code. As usual, Google is keeping the bug details private until most people have updated.

2. Who found these bugs

Google did most of the work: Google’s own teams reported 12 of the 21 fixes, including the one Medium bug. Xinyang Ge, who also reported all four Critical bugs in last week’s patch, is credited with four more here, including the new Critical one.

Outside researchers: the other five came from five different outside researchers, each credited with one High bug, including a V8 bug reported by Hyeonjun Ahn and a Network bug reported by Cristian Di Nicola.

Chart of the 21 fixes in Chrome 156.0.8078.79: 1 Critical, 19 High and 1 Medium, plus who reported them
How the 21 fixes break down by severity, and who reported them. Data: Google. Graphic: ChromeGeek

3. Which version you should have

PlatformVersion with the 21 fixesStatus
Windows and Mac156.0.8078.79/.80Rolling out
Linux156.0.8078.79Rolling out
Android156.0.8078.79 (Google Play)Rolling out
Chromebooks (ChromeOS Stable)Not listed yet. The October 28 build is 156.0.8078.77Pending

Chromebooks: Chrome on a Chromebook updates with ChromeOS itself, not on its own. Google’s October 28 ChromeOS Stable update moved Chromebooks to ChromeOS 16836.30.0 with Chrome 156.0.8078.77. That note lists nine fixes from last week’s 52-fix batch, including one of its Critical bugs, but none of the 21 fixes in this new update. Google has not posted a ChromeOS build with them yet, so check for updates again over the next few days.

Timeline of Chrome 156 security updates: 52 fixes on October 27, ChromeOS 156.0.8078.77 on October 28 and 21 fixes on October 29
Three Chrome 156 security releases in three days. Graphic: ChromeGeek

4. How to update Chrome now

  1. Windows, Mac and Linux: open Chrome, click the three-dot menu, then Help > About Google Chrome. Chrome checks for the update and downloads it.
  2. Click Relaunch when it appears. Your open tabs come back after the restart, but save anything you are typing first.
  3. Check the version on the same page. You want 156.0.8078.79 or later.
  4. Android: open the Play Store, search for Chrome and tap Update if you see it.
  5. Chromebook: go to Settings > About ChromeOS > Check for updates and restart if an update is waiting.

Not showing yet? Google rolls Chrome updates out in waves, so it can take a few days to reach everyone. Checking the About page usually pulls it in sooner.

Our take

Two security patches in one week can feel like a lot, but this is how it should work: bugs get found, fixed and shipped fast. This one is smaller than last week’s, yet it still has a Critical bug in the code behind video calls, so do not skip it. Restart Chrome and check for 156.0.8078.79. Chromebook owners are a step behind this time, so keep checking for the next ChromeOS update.


Discover more from Chrome Geek

Subscribe to get the latest posts sent to your email.

Sophie is a Chicago-based editor for Chrome Geek covering Chromebooks, Gemini, and the Google ecosystem. When she is offline, you can usually find her watching Blackhawks hockey or grabbing iced coffee in the city.