ChromeOS 16836.19.0 Stable: restart your Chromebook today

Updating Chrome on a Windows or Mac PC still does not patch a Chromebook. Chromebooks run ChromeOS, and Google ships that OS on its own Stable train. On Tuesday, October 20, 2026, Google moved ChromeOS Stable to OS version 16836.19.0, with browser build 156.0.8078.42.

If your daily machine is a Chromebook or a ChromeOS Flex PC, this is the package to install. It is a different story from desktop Chrome notes on Windows and Mac, and it is newer than our earlier ChromeOS 16805.33.0 Stable note.

What Google shipped

Google’s Stable Channel Update for ChromeOS / ChromeOS Flex (Tuesday, October 20, 2026) says M-156, ChromeOS version 16836.19.0 (browser version 156.0.8078.42), has rolled out to ChromeOS devices on the Stable channel.

The same post lists a long set of Chrome browser security fixes: 13 Critical, 87 High, 15 Medium, and 2 Low by my count. These are the 13 Critical items:

• CVE-2026-106347: use after free in Track
• CVE-2026-106358: use after free in Navigation
• CVE-2026-110151: use after free in Media
• CVE-2026-110148: use after free in SVG
• CVE-2026-110161: use after free in Network
• CVE-2026-110136: use after free in PDF
• CVE-2026-110149: use after free in Browser
• CVE-2026-110922: use after free in Prerender
• CVE-2026-113303: memory corruption in WebRTC
• CVE-2026-113271: use after free in Accessibility
• CVE-2026-113280: memory corruption in Paint
• CVE-2026-113072: memory corruption in CSS
• CVE-2026-113279: memory corruption in Accessibility

It also calls out High third-party / platform fixes, including:

• arc-keymaster: a fall-off-end undefined-behavior issue that can allow a guest-to-host wild indirect call
• mali_kbase: a double-free of dma_buf_attachment that can allow kernel memory corruption
• mali: a page-migration use-after-free that can allow unprivileged kernel memory corruption on mt8196

Under other third-party fixes, Google also lists a Medium item for compromised 3rd-party CA certificates that results in compromised TLS for all clients. The note does not name the CA, but it lands the same week as the eMudhra CA incident. Either way, a Chromebook gets this fix from the ChromeOS update.

Google’s post does not say these browser bugs are being exploited in the wild. Critical browser memory bugs plus High platform fixes are still enough reason to restart today.

Why this is not “I already updated Chrome”

Home readers mix these up constantly:

• Desktop Chrome on Windows, Mac, or Linux is a separate browser product. Recent desktop notes on this site cover builds like Chrome 155.0.8059.84.
• ChromeOS is the operating system on the Chromebook. This Stable drop carries browser 156.0.8078.42 inside the OS image.

If someone in the house updates Chrome on a Windows laptop, the Chromebook on the kitchen table does not follow. Check the Chromebook.

How to update and verify on your Chromebook

Google’s help page Update your Chromebook’s operating system is the checklist. In plain steps:

1. Turn the Chromebook on and connect it to Wi-Fi (plugged into power is better for a big download).
2. At the bottom right, open the time area, then open Settings.
3. Open About ChromeOS.
4. Under Google ChromeOS, read the current version. Select Check for updates if the button is there.
5. Let the download finish. When ChromeOS offers a restart (or you see an Update device notification), Restart so the new OS actually runs.
6. After reboot, return to About ChromeOS and confirm you are on 16836.19.0 (browser 156.0.8078.42) or newer on that Stable train.

Downloaded is not enough. The restart is the install. If Settings says you are up to date but the version is still older than 16836.19.0, wait for the staged rollout and check again later the same day. Google rolls Stable over days.

ChromeOS Flex PCs use the same About ChromeOS update path. School or work Chromebooks may show that updates are managed by an administrator. This article is for a personal Chromebook you control.

Do this / don’t do that

Do

• Open About ChromeOS, check for updates, and restart when offered.
• Confirm the OS line shows 16836.19.0 (browser 156.0.8078.42) after reboot.
• Treat Critical browser fixes and High platform fixes as “restart today,” not “maybe this weekend.”
• If the device is old, also check Additional details → Update schedule so you know when automatic updates end (Google’s update help).

Don’t

• Do not assume a Windows or Mac Chrome update covered the Chromebook.
• Do not leave the “update ready” notification sitting for days without restarting.
• Do not chase every CVE number on Google’s long list. Install the OS build and verify the version.
• Do not wait for exploit details. Google’s note does not say any of these bugs are being exploited, and patching is still the job.

Bottom line

Google’s October 20, 2026 ChromeOS Stable update moves devices to OS 16836.19.0 with browser 156.0.8078.42, including Critical browser fixes, High platform fixes, and a compromised CA certificate mitigation (official ChromeOS Stable note). On your own Chromebook: Settings → About ChromeOS → Check for updates, restart, then confirm the version. That is the whole job.

Image: Chromebook at home marketing photo (google.com/chromebook).