How many critical flaws did Chrome Extended Stable 152 fix for Windows and Mac?

Google has released Chrome Extended Stable 152.0.7977.169 for Windows and Mac, addressing ten security vulnerabilities. The update includes fixes for two critical flaws and eight high-severity issues. According to the official advisory, the rollout will occur over the coming days and weeks. This release targets organizations using the Extended Stable channel for longer-term support and stability.

Root cause

The two critical vulnerabilities are tracked as CVE-2026-110151 and CVE-2026-110922. CVE-2026-110151 is classified as a use-after-free error. CVE-2026-110922 is also rated critical. The eight high-severity flaws include CVE-2026-110144, which Microsoft describes as an incorrect authorization issue. Other high-severity fixes are tracked as CVE-2026-110159, CVE-2026-110166, CVE-2026-110172, CVE-2026-110913, CVE-2026-110918, CVE-2026-110919, and CVE-2026-110921.

Attack path

Google has not published specific details on how these vulnerabilities might be exploited. Access to bug details and links remains restricted until a majority of users have updated with the fix. Restrictions are also retained if the bug exists in a third-party library that other projects depend on but have not yet fixed. No evidence of active exploitation in the wild has been reported in the advisory.

Affected versions

Chrome Extended Stable 152.0.7977.169 is the patched version for Windows and Mac. Users on previous Extended Stable builds are vulnerable to these ten security issues. Microsoft Edge, which is Chromium-based, ingests Chromium fixes. According to Microsoft’s Security Update Guide, Edge addresses these vulnerabilities by incorporating the upstream Chromium patches. Administrators should verify their current browser versions against this patched build.

Mitigation

• Update Chrome Extended Stable to version 152.0.7977.169 on all Windows and Mac systems.
• Verify that Microsoft Edge and other Chromium-based browsers have received corresponding updates.
• Monitor internal systems for any unusual browser behavior during the rollout period.
• Ensure automatic update mechanisms are functioning correctly to deploy the patch.

What it means for organisations

Teams should verify that all managed endpoints have received the update, especially those on Extended Stable. Check whether internal applications rely on specific browser features that might be affected by security hardening. Communicate with suppliers who provide browser-based services to ensure their environments are also patched. Identify who within the IT team is responsible for monitoring deployment success and who should be alerted if updates fail. Establish a process to confirm that all browsers restart after updating to apply the fixes.

What to do and how to stay safe: Google Chrome

• Check your current Chrome version and update to 152.0.7977.169 if you are on Extended Stable.
• Verify that other Chromium-based browsers like Edge are updated to mitigate shared vulnerabilities.
• Monitor system logs for any errors related to the browser update process.
• Once the vendor provides an update, ensure all endpoints have successfully installed it.

Step-by-step guide: Patch Testing Best Practices That Prevent Production Failures

General security guidance from the CloudSec Press newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the version number of the patched Chrome Extended Stable release?

The patched version is 152.0.7977.169 for Windows and Mac.

How many critical vulnerabilities are fixed in this update?

Two critical vulnerabilities are fixed: CVE-2026-110151 and CVE-2026-110922.

Does Microsoft Edge also fix these vulnerabilities?

Yes, Microsoft Edge ingests Chromium fixes and addresses these vulnerabilities according to Microsoft.