Loading story…
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.
See real exploitation activity before you spend the cycle.
4 events from the most recent confirmed update back to the earliest known activity.
Google said the new cadence will begin with Chrome 153 on September 8, 2026, producing new beta and stable releases every two weeks. The Extended Stable channel for enterprises will remain on an eight-week cadence, and Chromebook users will keep extended release options.
Google said Chrome will shift from a four-week to a two-week release cycle for beta and stable channels on Desktop, Android, and iOS, while Dev and Canary schedules remain unchanged. The company said smaller, more frequent releases should reduce disruption, simplify debugging, and deliver fixes and features faster.
In August 2023, Google said Chrome would continue receiving weekly security updates to reduce the patch gap and limit the window for vulnerability exploitation.
Google previously reduced Chrome's major release cadence in 2021 from six weeks to four weeks, partly to speed delivery of security fixes.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
4 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcego.theregister.com
Open sourcehelpnetsecurity.com
Open sourcebleepingcomputer.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 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
Google released Chrome 153 for Windows, macOS, Linux, Android, and iOS, fixing 230 reported security vulnerabilities, including **CVE-2026-87491**, an out-of-bounds write in the V8 JavaScript and WebAssembly engine that is reportedly being exploited in the wild. The release includes five critical and 43 high-severity fixes across WebGL, Cast, ANGLE, PDFium, V8, and WebView; organizations should prioritize updating managed browsers to `153.0.8010.36` or later. Google has formally reduced Chrome's stable release cycle from four weeks to two weeks, aiming to shorten the N-day window between public disclosure of a flaw and deployment of a patch. The company cited a growing volume of reports and automated AI-assisted security work, alongside faster-moving AI-enabled threats, as drivers for the accelerated cadence; the schedule will also speed delivery and iteration of Chrome features, including AI capabilities.
Sep 10, 2026
Google has released **Chrome 151** to the stable channel, delivering a mix of user-facing, enterprise, and developer changes in the Chromium-based browser. The update adds new **Gemini** AI integrations, expands **Safe Browsing** protections, and improves PDF handling, while Google continues to distinguish Chrome from upstream Chromium through bundled components such as Google API integration, DRM support, and other Chrome-specific services. The release also keeps the **Extended Stable** channel available and indicates that **Chrome 152** is planned as the next major version. Chrome 151 also advances Google's transition away from legacy extensions by further restricting **Manifest V2** add-ons, though enterprises retain a temporary policy option to allow older MV2 extensions during migration. On the platform side, the browser drops support for **macOS 12** and now targets **macOS 13+**, while additional legacy browser features and APIs are being removed or deprecated, including older XML/XSLT-related functionality. The release further introduces web-platform updates for developers, including new HTML and `PerformanceObserver` capabilities, alongside broader changes affecting Windows, Linux, and macOS deployments.
Jul 30, 2026