Chrome 153 Starts a Two-Week Cycle Enterprises Skip

Chrome 153 hit stable on September 8, 2026, the first build on Google’s new two-week release cycle. The update is rolling out on desktop, Android and iOS as 153.0.8010.36 on Linux and 153.0.8010.36/.37 on Windows and Mac.

Consumer Chrome now moves every 14 days. The people who certify, embed and manage it still have an eight-week off-ramp that never even installs 153.

The First Two-Week Stable

Ben Mason and Deepak Ravichandran, writing for Chrome for Developers, said the company was putting a March plan into action with the launch of Chrome 153. Chrome 154 Beta is already out. Stable for 154 is set for September 22, 2026, 14 days after 153.

Chrome had shipped a new milestone every four weeks since 2021. In 2023 it added weekly security refreshes and an early stable slice to catch bugs before the full rollout. Dev and Canary do not change. Beta now tracks the faster stable train.

Chrome 152, the last build spaced on the old four-week gap, went stable on August 25, 2026, 28 days after Chrome 151 on July 28. The 152-to-153 gap is already 14 days. From here, a new stable and a new beta are supposed to land every two weeks.

Google’s public case is speed. Smaller drops should make a bad commit easier to find. Fixes that land in the public Chromium tree should reach phones and PCs before attackers have as long to study them. That is the consumer story. It is not the whole clock.

Enterprise Fleets Are Built to Skip 153

Chrome Enterprise still offers an eight-week Extended Stable channel for managed Windows and Mac browsers. Google keeps that milestone branch alive for six extra weeks and back-ports security fixes. A new Extended Stable milestone still ships every eight weeks, the same rhythm introduced in 2021.

Google’s own illustration of the new overlap is blunt. Stable walks 152, 153, 154, 155, then 156. Extended Stable sits on 152 for those same weeks and meets Stable again at 156. The note on the table says the numbers are examples, not a live calendar. Version 152 is a real build, and the pattern is the point: three consumer stables can pass before an Extended Stable fleet is asked to take a feature jump.

STABLE VS EXTENDED STABLE

For the first two weeks of a shared milestone, the two channels are identical. For the next six, Extended Stable gets weekly security refreshes “wherever technically possible.” Google still tells admins that two-week Stable is the more secure default when patch speed matters more than change-control cost.

The two-week Stable option becomes the most secure choice and should be used by most of your enterprise users. The Extended Stable channel is available for customers who cannot accommodate a two-week release cycle.

Ben Mason and Deepak Ravichandran, Chrome for Developers, September 8, 2026

That sentence is the split. Home users and most managed desktops are pushed onto 26 feature trains a year. Anyone who cannot restart, recertify or retest that often is invited to skip 153, 154 and 155, then take a larger jump at 156. Security fixes still flow. New web-platform behavior does not.

Microsoft Beat Chrome to the Fortnight

Google announced the two-week plan on March 3, 2026, and named Microsoft, Mozilla and Brave as peers now on the same idea. The shipping order ran the other way. Edge 152 reached Stable on August 27, 2026, as Microsoft’s first two-week major. Firefox 155 landed on September 1. Chrome 153 followed on September 8.

WHO SHIPPED THE TWO-WEEK STABLE FIRST

Mozilla’s director of engineering, Sylvestre Ledru, told the dev-platform list on July 9 that Firefox’s own two-week experiment would start with 155, aimed at September 1 instead of September 15. He wrote that work which is not ready should not be rushed, and that Mozilla would watch the results and adjust. Firefox ESR stays on the long enterprise train. Chrome’s Extended Stable is the closer cousin of that idea, on an eight-week rather than a yearly jump.

Brave’s public wiki already lists a Brave two-week stable calendar aligned to Chromium milestones. Chromium 153 as Brave 1.95.x was moved from September 10 to September 11. After that, Brave’s table steps 154 on September 22, the same day Chrome 154 is due. The Chromium number is now a shared fortnight, even when the product name on the icon is different.

230 Fixes on the Opening Build

The first two-week stable is not a light drop. Google’s desktop advisory for 153 lists 230 security fixes. The same note says access to bug details may stay restricted until most users have the patch, and that the rollout will take days to weeks. A Chrome 144 security update already taught the same lesson: the download is not the fix until the browser is closed and opened again.

THE 153 BUILD AT A GLANCE

• Stable versions: 153.0.8010.36 on Linux, 153.0.8010.36/.37 on Windows and Mac.
• Security load: 230 fixes in the September 8 desktop advisory.
• In-the-wild bug: Google says an exploit for CVE-2026-87491, a medium out-of-bounds write in V8, exists in the wild.
• Next stable: Chrome 154 on September 22, 2026.

The advisory’s critical list is heavy on graphics code. Four of the five critical bugs sit in WebGL (CVE-2026-87464, CVE-2026-87488, CVE-2026-87438, CVE-2026-87527). The fifth, CVE-2026-87628, is a use-after-free in Cast. CVE-2026-87491 is rated medium, and it is the one Google flags as already used. That pairing is why a 14-day stable clock is being sold as a security tool: the N-day window, the gap after a fix is visible in public code and before it reaches users, shrinks if the train leaves twice as often.

It also raises the cost of sitting on Extended Stable. Weekly backports still arrive. A V8 bug that needs a large change may not. Google’s enterprise help says complex fixes and large security features might ship only on two-week Stable.

What Changes for Developers Testing Sites?

Each stable now carries a smaller slice of the web platform, and it arrives twice as often. Isolation of a broken commit should get easier. The test burden moves the other way. A site that used to recertify against one Chrome milestone a month now has a new stable in the middle of that month, with the next beta already public.

Chrome 153’s own notes show what “smaller” still includes. Frontend teams will meet new CSS overflow behavior, a memory-safe Rust XML parser for non-XSLT work, and the removal of the non-standard _current navigation target. Early testers have also been poking at new camera and microphone elements, including a retry path that can keep an old permission error after a successful second request. Compatibility checks that ran once per four-week train now have to run on a 14-day clock if the goal is to catch those breaks before users do.

WHAT 153 PUTS ON THE PLATFORM

• Single-axis overflow: Scroll and clip can be set per axis, so sticky positioning can follow a different ancestor on each axis.
• Rust XML parser: Non-XSLT XML parsing moves to a memory-safe engine, with Google saying existing web standards still apply.
• Removed _current: Blink drops a non-standard navigation target that had little use on the live web.
• Beta already open: Chrome 154 Beta is the build to test against before September 22.

Google tells developers to watch the Chrome Status Roadmap and to keep a Beta install. Under the new spacing, that Beta is not a nice extra. It is the only window left between “landed in Chromium” and “shipping to Stable on a Tuesday.”

Chromebooks Are Still on Version 152

The two-week promise does not land on every Chrome-shaped product on the same Tuesday. Google said Chromebooks will keep extra platform testing, and that managed ChromeOS channels are being adapted, with more detail to come. On September 8, Chrome Releases was still pushing ChromeOS Flex stable to browser 152.0.7977.113. Phones and Windows PCs were already on 153. The Chromebook is on a third clock: not two-week Stable, not eight-week Extended Stable, but “after dedicated platform testing.”

Embedded Chromium is on a fourth. Microsoft told Windows app makers that the WebView2 Runtime two-week cadence starts with version 153 in the week of September 10. Evergreen Runtime follows Edge automatically. Fixed Version Runtime stays pin-able, and new majors simply arrive more often, so a pinned app that does not revalidate will fall behind on the same class of V8 and WebGL fixes Chrome just shipped. Chromium embedders can still take security backports from the Extended Stable branch even when the consumer Extended Stable installer is Windows and Mac only.

So the two-week web is already here, and it is several webs. Consumer Chrome, Edge, Firefox and Brave now share a fortnight. Enterprise Chrome can skip three stables. Chromebooks wait for a platform pass. WebView2 apps either ride Evergreen or take on a faster pin-and-test loop. Chrome 154 is due on September 22. The next choice for anyone who ships on top of Chromium is whether that date is a feature or a deadline.

Frequently Asked Questions

How Do IT Admins Turn On Chrome Extended Stable?

Managed Windows and Mac fleets switch with the TargetChannel policy. Windows also has MSI installers for Extended Stable, and Mac can use PKG or DMG packages. Google asks admins to try the channel on a small set of machines or org units before a fleet-wide move, because the feature set then lags Stable by up to six weeks even while weekly security refreshes continue.

Does Chrome Extended Stable Run on Phones?

No. Extended Stable is documented only for managed Chrome on Windows and Mac. It is not supported on iOS or Android, so a phone fleet that needs slower feature jumps has no Google channel equivalent and stays on the two-week Stable train once 153 is offered.

Do Weekly Chrome Security Updates Still Ship?

Yes. The two-week change is about major milestones, not the weekly refresh train that started in 2023. Both Stable and Extended Stable still get those refreshes, and Extended Stable is supposed to receive the same security fixes as Stable when a back-port is technically possible.

Do Chromium Embedders Get the Eight-Week Branch?

They get the security work from it. Google’s process notes say Extended Stable binaries are shipped to enterprises on Windows and Mac, while security fixes that apply to any Chrome Browser platform still land on that branch for embedders to pick up. Feature parity with consumer Stable is not part of that promise.

Chrome 154’s stable date is already on the public calendar: September 22, 2026. That is the first Tuesday that will show whether a two-week Chrome is a smaller drop, or just a faster one.