Skip to content
Wednesday, October 14, 2026AboutContactRSS
PatchReview
Bits, bytes and breaking security news
Vulnerabilities

Update Chrome 155 and 152 to Patch Critical Buffer Overflow and Use-After-Free Flaws

Google released security updates for Chrome Stable and Extended Stable channels, addressing dozens of vulnerabilities including critical memory corruption bugs.

Patch Review Newsroom ·
Update Chrome 155 and 152 to Patch Critical Buffer Overflow and Use-After-Free Flaws
Illustration: Patch Review

Key points

  • Chrome Stable version 155.0.8059.79/.80 fixes 37 security issues, including seven critical flaws.
  • Chrome Extended Stable version 152.0.7977.167 addresses 28 security issues, including five critical flaws.
  • Critical vulnerabilities include buffer overflows in ANGLE and use-after-free errors in browser components.

Google released new versions of Chrome for desktop users to address a large batch of security vulnerabilities. The Stable channel now runs version 155.0.8059.79/.80 on Windows and Mac and 155.0.8059.79 on Linux, while the Extended Stable channel updated to version 152.0.7977.167 for Windows and Mac. These updates roll out automatically over the coming days and weeks, according to official release notes.

In plain English

The updates fix problems that could allow attackers to execute code or crash the browser. The Stable channel patch includes 37 security fixes, with seven rated as critical. The Extended Stable channel update includes 28 fixes, with five rated as critical. Most of these critical issues involve memory corruption, such as buffer overflows or use-after-free errors, which occur when software accesses memory incorrectly.

The background

Specific critical flaws in the Stable update include a buffer overflow in the ANGLE graphics library and use-after-free bugs in the Browser, PDF, Network, Core, SVG, and Media components. Researchers from depthfirst, Google, and others reported these issues between late September and early October 2026. The Extended Stable update also fixes critical bugs identified in its respective release cycle.

What changes now

Users on the affected desktop platforms will receive the updates through Chrome’s automatic update mechanism. Google stated that access to detailed bug information remains restricted until a majority of users have installed the fixes. This restriction also applies if the vulnerability exists in a third-party library that other projects depend on but have not yet patched.

Who needs to act first

Teams managing public-facing endpoints should prioritize updating systems exposed to untrusted web content. Check whether automated update policies are functioning correctly before rolling out the new versions. Verify that backup solutions capture the current state of user profiles before applying the patch. Monitor internal logs for any unusual browser behavior after the update completes to ensure stability.

What to do and how to stay safe: Google Chrome

  • Verify your Chrome version in the settings menu to confirm you are running the latest release.
  • Restart your browser to ensure the security patches are fully applied and active.
  • Check group policy settings if you manage devices centrally to force immediate updates.
  • Monitor vendor announcements for any additional guidance on restricted bug details.

Step-by-step guide: Emergency Patching: How to Fix Critical Flaws Without Breaking Systems

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

Frequently asked questions

Which operating systems are affected by these updates?

Windows, Mac, and Linux are affected by the Stable channel update, while Windows and Mac are affected by the Extended Stable update.

Are there any critical vulnerabilities in the Extended Stable update?

Yes, the Extended Stable update includes five critical security fixes, according to the official advisory.

Why are bug details restricted?

Google keeps details restricted until most users update or if the flaw affects shared third-party libraries.

Sources

  1. Google Chrome Releases
  2. Google Chrome Releases
Google ChromeCVE-2026-110152CVE-2026-110149buffer overflowuse-after-free

You may also like