Severity
High
Analysis Summary
Google has released a new Chrome Stable Channel update, upgrading Windows and macOS to versions 151.0.7922.169/.170 and Linux to 151.0.7922.169. The update addresses 15 security vulnerabilities, including two critical buffer overflow flaws, CVE-2026-76034 and CVE-2026-76036, affecting Chrome’s graphics components. Google is rolling out the update gradually over the coming days and weeks and recommends that users install it as soon as it becomes available.
The most severe vulnerability, CVE-2026-76034, affects WebGL, Chrome’s technology for rendering interactive 2D and 3D graphics. A malicious website could potentially exploit specially crafted WebGL content to trigger memory corruption, potentially resulting in browser crashes, data corruption, or arbitrary code execution. The second critical flaw, CVE-2026-76036, is a buffer overflow in Dawn, Chromium’s implementation of the WebGPU standard. Since both WebGL and WebGPU process complex graphics data from web content, these vulnerabilities could present significant risks when users visit malicious or compromised websites.
Beyond the two critical flaws, Chrome 151 fixes 13 additional high-severity vulnerabilities involving CORS, CredentialProvider, USB, Core, Browser, Media, GPU, ANGLE, V8, Skia, and WebGL. These include use-after-free, type confusion, race condition, information leak, incorrect calculation, inappropriate implementation, and additional buffer overflow issues. Google credited its internal security teams and external researchers, including Raghav Maheshwari, ywatanabee, un3xploitable, GF, and OpenAI Codex Security with reporting several of the vulnerabilities. Google has not released technical details or proof-of-concept exploits for the critical issues, restricting access to bug reports until most users have received the fixes to make patch reverse-engineering and exploitation more difficult.
Organizations should prioritize deployment of the updated Chrome versions through their normal patch-management systems, particularly on endpoints frequently exposed to untrusted websites or graphics-intensive web applications. Users can manually check for the update by navigating to Chrome → Help → About Google Chrome, where Chrome will automatically check for the latest version and prompt for a restart if required. Security teams should also monitor browser-version compliance across managed Windows, macOS, and Linux systems and ensure that the updated Chrome 151 release is deployed across the environment.
Impact
- Gain Access
- Code Execution
Indicators of Compromise
CVE
- CVE-2026-76034
- CVE-2026-76036
- CVE-2026-76033
- CVE-2026-76037
- CVE-2026-76044
- CVE-2026-76039
- CVE-2026-76040
- CVE-2026-76035
- CVE-2026-76042
- CVE-2026-76046
- CVE-2026-76043
- CVE-2026-76041
- CVE-2026-76047
- CVE-2026-76038
- CVE-2026-76045
Remediation
- Update Google Chrome to version 151.0.7922.169/.170 on Windows/macOS and 151.0.7922.169 on Linux as soon as the update becomes available.
- Enable automatic Chrome updates to ensure security patches are installed promptly.
- Restart Chrome after the update to complete the installation.
- Prioritize patching managed endpoints through enterprise patch-management and software deployment systems.
- Verify Chrome version compliance across Windows, macOS, and Linux endpoints.
- Restrict access to untrusted or suspicious websites, especially those using complex WebGL or WebGPU content.
- Monitor endpoint security logs for unusual Chrome crashes, abnormal browser behavior, or suspected exploitation attempts.

