1-minute read of a 5 min report

Chrome Fixed 1,072 Bugs, Then Changed How Updates Reach Users

By

1-minute read

What a defender needs to know

Google says Chrome 149 and 150 fixed 1,072 security bugs, more than the previous 23 milestones combined. The number reflects an AI-scaled discovery and remediation pipeline, not 1,072 critical or actively exploited flaws. Google now uses models for discovery, report reproduction and enrichment, candidate fixes, critic review, and test writing while developers retain review.

Google is moving toward two-week milestones, weekly security updates, and a pilot of two security releases per week. The remaining exposure can sit on the endpoint: Chrome may download and stage new binaries but leave the running browser on the old version until it restarts. Chrome 150 added an opportunistic no-window restart on macOS; general dynamic patching remains research.

Set a relaunch deadline with RelaunchNotification, inventory the running Chrome version across the fleet, and distinguish downloaded updates from applied ones. Investigate devices that miss the deadline for disabled updates, persistent processes, failed relaunches, unsupported systems, or policy conflicts.

For each security release, define the fixed Stable version and a compliance deadline. Preserve the last update and relaunch time for lagging devices, and do not hide long-lived exceptions inside an average deployment percentage. Extended Stable may support controlled environments, but it does not make a pending security update safe to defer indefinitely.

Verify that every in-scope device reports the approved running version. Record an owner, compensating control, and expiration date for each exception. A staged package, cached installer, or successful download event is not proof that the browser is protected.

Primary sources