Chrome 156.0.8078.73: install today's Stable security update

If chrome://version still shows 156.0.8078.47 or .48, you are not done. On Tuesday, October 27, 2026, Google shipped another Stable channel security update for Chrome 156. The builds to look for now are:

• Windows / Mac: 156.0.8078.73 or 156.0.8078.74
• Linux: 156.0.8078.73
• Android: 156.0.8078.73 (rolling out on Google Play)

This follows our Chrome 156 Stable .47/.48 note. Same Chrome 156, newer build, new Critical fixes. Updating Edge or Firefox does not update Chrome.

What Google shipped on October 27

Google’s Stable Channel Update for Desktop says the Stable channel was updated to 156.0.8078.73/.74 for Windows and Mac and 156.0.8078.73 for Linux, rolling out over the coming days and weeks. The same note says the update includes 52 security fixes.

Google rates four of them Critical:

• CVE-2026-118306: Memory corruption in FileSystem (reported by Xinyang Ge of Anthropic, assisted by Claude)
• CVE-2026-118331: Improper input validation in FileAPI (reported by Xinyang Ge of Anthropic, assisted by Claude)
• CVE-2026-118348: Improper input validation in Skia (reported by Xinyang Ge)
• CVE-2026-118344: Use after free in Layout (reported by Xinyang Ge)

Most of the rest are rated High, spread across FileSystem, V8, Turbolev, Animation, HTML, ANGLE, Skia, Forms, Cache, Paint, WebRTC, Video, WebAudio, Payments, Media, PDFium, SVG, and more. You do not need to memorize the list. Four Critical fixes plus fifty-two security fixes in one update is enough reason to install, fully quit, and relaunch.

Google’s note does not say any of these bugs are being exploited in the wild. The number and severity of the fixes are reason enough to update. Malwarebytes covered the same October 27 Chrome update the next day.

The same day’s Chrome for Android Update released Chrome 156 (156.0.8078.73) for Android, arriving on Google Play over the next few days. Google says Android releases contain the same security fixes as the matching desktop builds unless noted otherwise.

Why .47/.48 is not enough anymore

Our note on the October 20 Stable release was correct for its day. .47/.48 carried 353 security fixes. It does not include this October 27 set.

• 155.0.8059.x is a full version behind.
• 156.0.8078.12/.13 (the October 7 Early Stable rollout) and 156.0.8078.47/.48 (October 20 Stable) are older 156 builds now.
• 156.0.8078.73/.74 is the October 27 security update.

Same habit every time:

1. Update
2. Fully quit and relaunch
3. Prove it with chrome://version

Downloaded is not running. The version page 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 156.0.8078.73 or .74 (Linux: .73).
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 156.0.8078.73 or 156.0.8078.74 (Linux: .73), or a newer 156 Stable build if Google has already moved past this one.
7. Repeat on other computers you use, including the laptop that sleeps with Chrome still open and any shared family PC.

If About Chrome does not offer .73/.74 yet, give it a day, then check again. Google rolls these out over days or weeks. Stick with Google’s own updater instead of third-party Chrome installers.

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 156.0.8078.73 when it appears.
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. Chrome on iPhone and iPad updates through the App Store on its own schedule.

Chromebooks update separately too. Updating the Chrome browser on Windows or Mac does not update ChromeOS.

Edge and other Chromium browsers

Microsoft Edge, Brave, and other Chromium-based browsers ship their own builds. Updating Chrome does not update them. Microsoft’s Edge security release notes for October 27, 2026 say Microsoft is aware of the recent Chromium security fixes and is actively working on releasing a security fix. When that Edge update lands, update Edge the same way you update Chrome: About Microsoft Edge, relaunch, then check edge://version.

Do this / don’t do that

Do

• Move to 156.0.8078.73/.74 and confirm with chrome://version.
• Fully quit Chrome after the update so old processes are gone.
• Update Android Chrome from Google Play on its own.
• Update Edge, Firefox, Safari, and Brave separately if you use them.

Don’t

• Do not stay on .47/.48 and assume you already “did Chrome 156.”
• Do not download Chrome installers from third-party download sites.
• Do not ignore the computer that only gets used when someone else in the house opens it. That is often the outdated one.

Bottom line

On October 27, 2026, Google moved Chrome Stable to 156.0.8078.73/.74 with 52 security fixes, including four Critical issues (Chrome Releases), and shipped the matching 156.0.8078.73 Android build. On your own PC or phone: install, relaunch, and verify chrome://version. Last week’s .47/.48 update was worth doing. This week’s build is the new finish line.

Image: Official Google Chrome horizontal logo with wordmark (google.com/chrome) on a light gray background.