Skip to content
PatchBriefing

Search PatchBriefing

Type at least two characters. Results update as you type.

Search CVEs, products, packages and article titles.

Nothing found. Identifiers such as CVE and GHSA can be searched in both languages.

Subscribe
154.0.8037.57
RELEASE SECURITY Browsers Google Chrome · released September 22, 2026 · covered September 22, 2026

Google Chrome 154.0.8037.57 Rolls Out with 108 Security Fixes

Chrome 154 has been promoted to the stable channel for Windows, Mac and Linux, bundling 108 security fixes alongside general improvements.

108 security fixes Stable for Windows, Mac, Linux Staged rollout over coming weeks
AI summary

Google has promoted Chrome 154 to the stable channel for Windows, Mac and Linux, identified as version 154.0.8037.57 on Linux and 154.0.8037.57/.58 on Windows and Mac. The rollout will happen gradually over the coming days and weeks. This release is notable primarily for its security content, making it relevant to every Chrome user and to site owners who rely on Chromium-based browsers for testing or deployment.

What's in this release

Alongside a broader set of fixes and improvements detailed in Chrome's internal change log, this update includes 108 security fixes. Google's release notes indicate that some bug details and reward amounts remain restricted, a standard practice while a fix is still rolling out to the majority of users or while an underlying third-party library dependency is still being patched across affected projects. Google has indicated that separate blog posts covering new features and larger engineering efforts in Chrome 154 are expected to follow.

Why it matters

A security update carrying 108 fixes is a substantial batch, even though individual CVE details are not yet public for all of them. Because Chrome and other Chromium-based browsers share code, this kind of update is relevant not just to everyday users but also to developers and site owners who test against Chrome or embed Chromium components, since unpatched browsers can be a vector for exploitation regardless of how secure a site's own code is.

How to update

Chrome generally updates itself automatically in the background; users can force the process by opening the three-dot menu and navigating to Help > About Google Chrome, which also triggers a check for the latest version and a relaunch prompt once it's downloaded. Given the security nature of this release and the staged, multi-day rollout, it's good practice to manually trigger an update check rather than wait for the automatic cycle, particularly on machines used for sensitive browsing or development work.

Synthesized by AI from 1 source · updated 2 hours ago
Sources · merged by AI 1 total
The Morning Brief

Relevant changes for the stacks you follow.

Choose your stacks, topics and optional WordPress plugins. At 07:00 CEST, matching advisories and releases from the reporting period are grouped into one email.

✓ Choose stacks and topics✓ Change preferences anytime✓ One grouped email