Google started rolling ChromeOS 158 out to the Stable channel on Wednesday, November 18, and it is reaching Chromebooks and ChromeOS Flex machines in stages. You won’t find anything new on screen, but there is a lot to patch: 400 browser fixes and eight fixes in ChromeOS itself, two of them for flaws that could let code break out of a virtual machine.

Install this one as soon as it appears. It’s a security release, so there are no new features to wait for.
Which version to look for
The build is platform version 16868.24.0 with Chrome 158.0.8127.65, as listed in Google’s Stable channel update for ChromeOS. Most devices are coming straight from ChromeOS 156, which was running Chrome 156.0.8078.102.
ChromeOS 157 never reached Stable, and it was never going to. Under the current schedule, only even-numbered milestones are promoted to Stable, and odd-numbered ones skip it. That explains why Chrome 157 reached Googlebooks, which get browser updates separately, while Chromebooks never got it.
What the update fixes
The browser fixes break down as 12 Critical, 169 High, 120 Medium and 99 Low. Most of the Critical bugs are use-after-free flaws in rendering components such as Layout, CSS and WebAudio. The others are buffer overflows and out-of-bounds writes in Dawn, ANGLE, the GPU code and Media.
The ChromeOS list is shorter, and it matters more to Chromebook owners. CVE-2026-74580, rated High, is a VM escape that also allows local privilege escalation. CVE-2026-99999, rated Medium, is a second VM escape. Linux apps and Android apps both run inside virtual machines on a Chromebook, so these fixes apply to anyone who uses either. Two related fixes harden crosvm, the virtual machine monitor. One closes a SafeFD bypass in VmConcierge that allowed option injection into crosvm, and the other stops crosvm’s disk-format auto-detection from exposing arbitrary host files.
The other ChromeOS fixes cover:
- a Linux kernel advisory (CVE-2026-98432)
- a newline injection into ARCVM boot properties through a synced app’s locale
- a symlink bug in the audio stack that let the chronos user destroy or take over arbitrary files as root
- a compromised third-party CA certificate that undermined TLS
Fixes for the Android side are published separately in the November 1 Android security bulletin. Devices on the long-term support channel get their own patch releases, such as the recent LTS-150 update that closed six critical flaws.
No release notes yet, and one feature has slipped
Google hasn’t published consumer “What’s New” notes for ChromeOS 158. Its Chrome Enterprise and Education release notes for ChromeOS still end at version 156. That page also changes the timing of one feature. Isolated Web Apps were due to let you check for updates manually and to notify you when one is available. Google first said this could come as early as ChromeOS 158, and the page now says ChromeOS 159. Automatic updates for these apps carry on in the meantime.
Because 159 is an odd-numbered milestone, Chromebooks on Stable probably won’t get that change before ChromeOS 160.
Planning for the next milestone has already started: the Chrome 159 admin release notes add a policy controlling Gemini file uploads on some ChromeOS devices.
How to get it now
The rollout is gradual, so your Chromebook might not show the update yet. On managed devices, an administrator may also be holding updates back. To check yourself, open Settings, select About ChromeOS, then select Check for updates. Save your work and restart when asked, then check that the version number starts with 158.
