Chrome 156 Stable: update past Early Stable to 156.0.8078.47

If Chrome is still on 155, or stuck on an early 156.0.8078.12/.13 build, you have a new target. On Tuesday, October 20, 2026, Google promoted Chrome 156 to the Stable channel for Windows, Mac, and Linux. The builds to chase are:

• Windows / Mac: 156.0.8078.47 or 156.0.8078.48
• Linux: 156.0.8078.47

That is the broad Stable rollout, not the limited Early Stable peek from October 7. Early Stable was a small cohort on .12/.13. Everyone else should now move toward .47/.48 as Google stages the update.

What Google shipped

Google’s Stable note says the update includes 353 security fixes. Among the named items are six Critical issues:

• CVE-2026-113341: Memory corruption in Skia (Google)
• CVE-2026-113279: Memory corruption in Accessibility (Xinyang Ge)
• CVE-2026-113072: Memory corruption in CSS (Xinyang Ge)
• CVE-2026-113280: Memory corruption in Paint (Xinyang Ge)
• CVE-2026-113271: Use after free in Accessibility (Xinyang Ge of Anthropic, assisted by Claude)
• CVE-2026-113303: Memory corruption in WebRTC (OpenAI Codex Security)

There is also a long High-severity list (Site Isolation, FileSystem, ANGLE, Passwords, V8, and more). You do not need to memorize the CVEs. Six Criticals plus a 353-fix Stable jump is enough reason to install, fully quit, and relaunch.

Google does not say these bugs are being exploited in the wild in that Stable note. Treat the volume and severity as the reason to update anyway.

The same day, Google released Chrome 156.0.8078.47 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 Early Stable .12/.13 is not enough

Our Chrome 156 Early Stable article covered the October 7 limited rollout. That post was correct for its day. It is not today’s finish line.

• 155.0.8059.x (including the October 15 .84/.85 package) is behind the new major train.
• 156.0.8078.12/.13 (desktop Early Stable) and 156.0.8078.25 (early Android) are old 156 builds.
• 156.0.8078.47/.48 is the October 20 Stable security set.

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 156.0.8078.47 or .48 (Linux: .47).
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.47 or 156.0.8078.48 (Linux: .47).
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 .47/.48 yet, give Stable a day, then check again. Google stages these over days or weeks.

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.47 when it appears. Google said it would roll out over the next few days after the October 20 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.

Chromebook owners are on a different train. ChromeOS Stable for this wave was covered separately in our ChromeOS 16836.19.0 note. Updating the Chrome browser app on Windows does not update ChromeOS.

Do this / don’t do that

Do

• Move to 156.0.8078.47/.48 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.
• Keep an eye on extensions for a day after a major train jump.

Don’t

• Do not stay on Early Stable .12/.13 and assume you already “did 156.”
• Do not sideload random Chrome installers from third-party download sites.
• Do not ignore a machine that only runs when someone else in the house opens it. That is often the outdated one.

Bottom line

On October 20, 2026, Google moved Chrome 156 to full Stable as 156.0.8078.47/.48 with 353 security fixes, including six Critical issues (Chrome Releases). On your own PC or phone: install, relaunch, and verify chrome://version. Early Stable was a preview. .47/.48 is the build that matters now.

Image: Official Google Chrome logo (google.com/chrome) on a plain light background.