Google published a new Long Term Support update for ChromeOS on July 8, 2026, and most Chromebook owners will never see it land. LTS-144 doesn’t bring a single new feature. Its entire purpose is patching ten security vulnerabilities, two of them critical, on devices that IT administrators have deliberately frozen on an older build of the operating system.
What the update actually fixes
According to the official Chrome Releases blog, LTS-144 (Platform Version 16503.90.0) addresses CVE-2026-8514 and CVE-2026-12443, both critical-severity use-after-free bugs in Aura and Web Authentication respectively, plus eight high-severity issues covering Extensions, InterestGroups, video and audio codecs, WebAudio, the GPU process, and the DOM. None of the ten are flagged as actively exploited in Google’s writeup, which is the detail security teams tend to watch for most closely.
Why this build is still called “144” in July
The version number is the interesting part here. ChromeOS 144 first reached the regular Stable channel back in January 2026, the same release that brought Gemini in Chrome to Chromebook Plus devices. Stable channel Chromebooks have since moved through several more feature releases and picked up ChromeOS 149 in early July. Devices on Long Term Support haven’t moved an inch, and that’s by design, not neglect.
Per Google’s own documentation, LTS locks a device’s feature set for six months at a stretch while still delivering targeted security fixes roughly every two weeks in between. It’s a trade-off Google built specifically for kiosks, unattended devices, and standardized testing setups in schools, where an admin would rather freeze the software than risk a surprise interface change mid-semester. Google is upfront about the cost: some critical fixes can take up to nine months to reach the LTS channel after they’ve already been fixed elsewhere, simply because the underlying code has drifted too far apart. Stability has a real price, and it’s paid in patch latency.
Who this actually affects
If you bought your own Chromebook and never touched the channel settings, you’re almost certainly on Stable, and this release doesn’t apply to your device at all. You’d already have picked up equivalent fixes through ChromeOS 149’s much larger security patch earlier in July. LTS only shows up on devices an organization has deliberately enrolled and pinned, and switching channels on a managed Chromebook is usually locked out for regular users anyway, as covered in our guide to ChromeOS update channels.
Where it does matter is for whoever manages those devices: a school running library catalog kiosks, a clinic with shared intake tablets, or a business with unattended lobby displays. Two critical bugs sitting unpatched across a fleet is exactly the scenario Long Term Support exists to prevent, so this isn’t an update worth pushing to the next maintenance window.
What Chromebook owners should do
For a personal device, there’s nothing extra to do beyond your usual routine: open Settings, go to About ChromeOS, and click “Check for updates” if you haven’t restarted in a while. If you administer enrolled Chromebooks on the LTC or LTS channel through the Google Admin console, push LTS-144 now instead of waiting for the next scheduled cycle, given the two critical CVEs involved. Either way, this is a good prompt to check which channel your own device is actually on, using that same Settings page, before assuming an update headline applies to you.
LOG 1 report