Key points
- The update addresses CVE-2026-110151 and CVE-2026-110922, both rated critical.
- Eight additional vulnerabilities are rated high severity in this release.
- The rollout targets Windows and Mac systems on the Extended Stable channel.
Google has released version 152.0.7977.169 for the Chrome Extended Stable channel on Windows and Mac. This update contains fixes for ten security vulnerabilities. Two of these issues are rated critical, while the remaining eight are rated high. The rollout will proceed over the coming days and weeks, according to the official advisory from Google Chrome Releases.
In plain English
The two critical flaws are tracked as CVE-2026-110151 and CVE-2026-110922. The eight high-severity issues include CVE-2026-110144, CVE-2026-110159, CVE-2026-110166, CVE-2026-110172, CVE-2026-110913, CVE-2026-110918, CVE-2026-110919, and CVE-2026-110921. Google states that access to detailed bug reports and links remains restricted. These restrictions stay in place until a majority of users have updated their browsers.
The background
Microsoft Security Update Guide lists CVE-2026-110144 as an incorrect authorization flaw and CVE-2026-110151 as a use-after-free issue. Microsoft notes that Edge, which is based on Chromium, ingests these fixes from the upstream project. Details on the specific components affected by the other eight CVEs are not provided in the current advisory. Bug tracker access is limited to protect users who have not yet patched their systems.
What changes now
Teams managing Extended Stable deployments should verify that version 152.0.7977.169 is installed on Windows and Mac endpoints. The update is available now but will distribute gradually. Administrators can check their deployment logs to confirm adoption rates. No further details on exploitation or wild activity are provided in the source material at this time.
Who needs to act first
Security operations teams usually prioritize systems with direct internet exposure or those handling sensitive data. Verify that endpoint management tools are pushing the latest version to all managed devices. Test the update in a small group first to ensure stability before a full rollout. Back up critical browser profiles or enterprise policies if possible. Monitor logs for any unusual activity during the update window to catch potential issues early.
What to do and how to stay safe: Google Chrome
- Verify that all Windows and Mac machines are running version 152.0.7977.169 or later.
- Check for pending updates in the browser settings to trigger manual installation if needed.
- Monitor internal logs for any error messages related to browser crashes or updates.
- Once the vendor provides an update for other channels, plan to apply it to those fleets as well.
Step-by-step guide: 7 Configuration Errors That Expose Systems to Zero-Day Exploits
General security guidance from the Vuln Post newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Does this update fix any critical vulnerabilities?
Yes, the update addresses two critical flaws, CVE-2026-110151 and CVE-2026-110922.
Is there a fix available for Microsoft Edge?
Microsoft states that Edge ingests Chromium fixes, so the vulnerability is addressed in Edge updates.
Why are bug details restricted?
Google keeps details restricted until a majority of users have updated to prevent exploitation.
