Should You Update to ChromeOS 151 Right Away?

ChromeOS 151 is rolling out with a bookmark bar auto-hide, Safe Browsing for Gemini, and 18 security fixes. What changed, and why you should update now.
Brand:Google
New ChromeOS system update 151

Google began rolling out ChromeOS 151 to Chromebooks and ChromeOS Flex devices on the Stable channel on August 14. The update ships as OS version 16733.48.0 with browser version 151.0.7922.141, and the biggest reason to install it is not a new feature: it closes 18 security vulnerabilities.

The patched flaws are tracked under individual CVE numbers and sit in core parts of the system. The list includes an integer overflow in Mojo, the internal messaging layer, filed as CVE-2026-13281, plus use-after-free bugs in the Aura window manager, the DOM, Payments, and Web Authentication, and a flawed WebGL implementation. These are memory handling errors, the class of bug attackers most often turn into working exploits, which is why a same-week update is the sensible move even on a machine that feels fine.

The visible change most people will meet first is the bookmark bar. Under Settings and then Appearance, ChromeOS 151 adds controls that let Chrome hide the bar automatically when you rarely touch it on the New Tab page. This is behavior based rather than a plain on-off switch: the browser watches whether you actually use the bar, tucks it away if you do not, and shows a small notice that brings it back permanently with one click. School and business administrators can pin the bar in place across managed devices through the BookmarkBarEnabled policy.

Gemini sessions in Chrome also pick up a safety net. ChromeOS 151 runs real-time Safe Browsing checks while Gemini summarizes pages, reads documents, or automates web tasks, so freshly registered scam domains and deceptive redirect chains get flagged during the AI session itself rather than only on normal page loads.

ChromeOS Flex users get the hardest news in this release. Machines with Intel or AMD graphics from 2010 and older, or Nvidia graphics from 2014 and older, stop receiving updates at this milestone. Those devices stay pinned on ChromeOS 150, which keeps working but will not move forward. If you converted an old PC or Mac with one of these chips, 151 is the point where updates stop.

Two smaller changes land for managed fleets. Legacy packaged Chrome Apps no longer launch in Kiosk mode, so signage and testing kiosks built on them must move to Progressive Web Apps; the same apps keep working inside standard user and managed guest sessions for now. Separately, the URLBlocklist policy is now enforced strictly inside Incognito windows, closing a loophole where allowlist entries could override blocks in private tabs. We track platform updates like this in our Operating Systems section, most recently the Windows 11 26H2 update rundown.


What to do on your Chromebook

Open Settings, choose About ChromeOS in the bottom left, and click Check for updates. Google staggers its rollouts, so the update may take a few days to reach your device. Given the size of this security batch, install it as soon as it appears rather than waiting for the next restart to catch it. Flex owners on the frozen GPU list have no update to chase; your machine stays on 150, and the practical decision now is whether that box becomes an offline workhorse or gets replaced.

tags:
Share:
Founder & Editor-in-Chief

Nasreddine is the founder of Softoto, a software download library and blog covering Windows, Mac, and mobile software. He spends his days verifying installers, tracking version histories, and separating real developer downloads from the fakes that outrank them. He tests what he can install himself, sources the rest from developer changelogs and advisories, and always says which one it was. Questions or corrections: contact@softoto.com

Discussion

(0)
{{ reviewsTotal }}{{ options.labels.singularReviewCountLabel }}
{{ reviewsTotal }}{{ options.labels.pluralReviewCountLabel }}
{{ options.labels.noReviewsLabel }}
{{ options.labels.newReviewButton }}
{{ userData.canReview.message }}