CyberSecurity News

Google Patches Critical Chrome WebGL and Dawn Flaws

Key Takeaways Google has issued an urgent update for Chrome, addressing two critical security flaws. The vulnerabilities, identified as buffer overflows, affect WebGL and Dawn, core graphics...

David kimber
David kimber
August 19, 2026 3 Min Read
2 0

Key Takeaways

  • Google has issued an urgent update for Chrome, addressing two critical security flaws.
  • The vulnerabilities, identified as buffer overflows, affect WebGL and Dawn, core graphics components within the browser.
  • Exploitation of these flaws could lead to browser crashes, data corruption, or potentially arbitrary code execution.
  • Users are advised to update their Chrome browsers immediately to version 151.0.7922.169/.170 (Windows/macOS) or 151.0.7922.169 (Linux).

Google Addresses Critical Graphics Vulnerabilities in Chrome Update

Google has rolled out a crucial Stable channel update for its Chrome browser, patching two critical security vulnerabilities residing in graphics-related components. Users are strongly urged to update their browsers without delay to mitigate potential risks.

Table Of Content

The latest update elevates Chrome to version 151.0.7922.169/.170 for Windows and macOS users, while Linux users will receive version 151.0.7922.169. Google has indicated that this release will be deployed incrementally over the coming days and weeks.

Deep Dive into the Critical Flaws

The two most severe issues addressed are tracked under CVE-2026-76034 and CVE-2026-76036. Both are classified as buffer overflow vulnerabilities. This type of memory safety flaw occurs when a program attempts to write more data into a fixed-size buffer than it can hold, overwriting adjacent memory regions.

Such vulnerabilities can have serious consequences, ranging from browser instability and data corruption to the potential for arbitrary code execution under specific attack scenarios. CVE-2026-76034 specifically targets WebGL, which is Chrome’s foundational interface for rendering interactive 2D and 3D graphics directly within web pages.

WebGL is extensively utilized by online games, sophisticated data visualizations, browser-based design applications, and other web applications that rely heavily on graphics processing. A malicious website could potentially exploit this flaw by delivering specially crafted WebGL content to a vulnerable browser.

The second critical vulnerability, CVE-2026-76036, is a buffer overflow found within Dawn. Dawn represents Chromium’s implementation of the WebGPU standard, a more modern graphics API designed to offer web applications more direct and efficient access to underlying graphics hardware.

Given that both WebGPU and other integrated graphics components process complex data streams originating from web content, memory corruption issues within these areas pose a significant and direct threat to browser security.

Disclosure and Remediation Efforts

Google’s internal security team was responsible for reporting both critical flaws, with CVE-2026-76034 identified on July 15, 2026, and CVE-2026-76036 on July 28, 2026. Consistent with standard security practices, Google has refrained from publicly disclosing technical specifics, proof-of-concept code, or details regarding potential exploitation methods.

Access to detailed bug reports will remain restricted until a substantial majority of Chrome users have applied the necessary fixes. This strategic delay aims to minimize the window of opportunity for threat actors to reverse-engineer the patches and develop exploits for these vulnerabilities.

In total, the Chrome 151 Stable release includes 15 security fixes. Google also highlighted its proactive use of advanced memory-error detection and fuzzing technologies, including AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL, to proactively identify security vulnerabilities during the software development lifecycle.

<td class="has-text-align-left

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.

Tags:

AttackCVEExploitPatchSecurityVulnerability

Share Article

David kimber

David kimber

David is a penetration tester turned security journalist with expertise in mobile security, IoT vulnerabilities, and exploit development. As an OSCP-certified security professional, David brings hands-on technical experience to his reporting on vulnerabilities and security research. His articles often feature detailed technical analysis of exploits and provide actionable defense recommendations. David maintains an active presence in the security research community and has contributed to multiple open-source security tools.

No Comment! Be the first one.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

CVE ID Severity Vulnerability type Affected component Reporter Issue ID
CVE-2026-76034 Critical Buffer overflow WebGL Google 534923522
CVE-2026-76036 Critical Buffer overflow Dawn Google 540087398
CVE-2026-76033 High Inappropriate implementation CORS Google 516715010
CVE-2026-76037 High Link following CredentialProvider Google 517612295
CVE-2026-76044 High Race condition USB Google 522732244
CVE-2026-76039 High Incorrect reference resolution Core Google 525167753
CVE-2026-76040 High Use-after-free Browser Google 534862220
CVE-2026-76035 High Inappropriate implementation Media Google 536439844
CVE-2026-76042 High