Loading story…
Google has confirmed that ChromeOS will receive regular updates and security patches through 2034 as it prepares to transition the Chromebook ecosystem to Googlebook OS. ChromeOS devices generally follow a 10-year automatic-update lifecycle measured from the launch of their hardware platform, meaning some older Chromebooks may lose support before 2034 while newer models could remain supported beyond that date.
Google said eligible newer devices will be able to migrate directly to Googlebook OS, but has not disclosed supported models, hardware requirements, or the upgrade process. Existing ChromeOS Enterprise Upgrade and Education Upgrade licenses will remain valid; however, organizations migrating devices or buying Googlebook systems will need new licensing under terms not yet announced. Enterprise and education management capabilities for Googlebook OS are planned for the second half of 2027.
Map this exposure pattern across your cloud, code, and identities.
1 event from the most recent confirmed update back to the earliest known activity.
Google updated its support documentation to state that ChromeOS will receive updates and security patches through 2034, while existing devices remain supported according to their individual automatic-update lifecycles. It also said eligible newer Chromebooks with lifecycles extending beyond 2034 will be supported in transitioning to Googlebook OS, without identifying eligible models, hardware requirements, or the migration process.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See where this exposure pattern shows up across your cloud, code, supply chain, and non-human identities.
2 references tracked. Mallory keeps watching after this page renders.
zdnet.fr
Open sourcetomshardware.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google announced it will shift **Chrome** from a four-week to a **two-week** release cycle for **Stable** (and corresponding **Beta**) builds across **desktop, Android, and iOS**, starting with **Chrome 153** scheduled for **September 8**. Google said the more frequent releases will be smaller in scope, aiming to reduce user disruption and simplify post-release debugging while maintaining stability due to internal process improvements. For enterprises, Google is not changing the **Extended Stable** option, which will continue on an **eight-week** cadence for organizations that prioritize longer validation windows. Google’s enterprise guidance positions the new fortnightly Stable cadence as the “most secure option” when security outweighs maintenance overhead, while noting that Chrome’s existing model of **weekly security updates** (introduced to reduce the “patch gap”) remains in place alongside the milestone releases.
Jun 29, 2026
Leaked screenshots and a screen recording from a Chromium Issue Tracker bug report revealed an early look at Google’s internal **“Aluminum OS” (ALOS)** project—an apparent desktop-oriented Android build tied to Google’s long-running effort to consolidate **Android and ChromeOS** into a single platform. The report was subsequently made private, but not before the media captured the visuals, which are described as the first “official” visual evidence of the desktop Android interface. The leak indicates the build `ZL1A.260119.001.A1` running on an HP Elite Dragonfly/HP Chromebook-class device using an Intel 12th-gen (Alder Lake-U) x86 processor, suggesting testing on existing Chromebook hardware. Visible UI changes include a desktop-style bar optimized for larger screens (with time/date placement changes), desktop multitasking (side-by-side), and **Chrome with extension support**; one account also notes prominent **Gemini** and screen-recording icons, implying potential “AI-native” integration. Overall, the material points to a ChromeOS successor or alternative desktop experience built on Android rather than a conventional ChromeOS evolution.
Jun 29, 2026
Google has shifted Chrome desktop and mobile releases from a four-week to a two-week cadence, shortening the time between public Chromium fixes and their availability to users. The company cited faster vulnerability discovery, exploit development, and spearphishing enabled by advanced and agentic AI, and said it is testing delivery of two security updates per week. Google is also developing dynamic patching intended to reduce or eliminate browser-restart requirements. Organizations using Chrome Enterprise's **Extended Stable** channel will continue to receive major releases every eight weeks, but critical security fixes will be backported and deployed weekly. Security teams should verify that managed Chrome fleets can receive interim security updates promptly and reassess patch-compliance monitoring as Chrome's release cadence increases.
Sep 17, 2026