External risk intelligence

Google Chrome ANGLE Out of Bounds Write Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79131

The vulnerability exists in a web browser, which is an application primarily designed to process untrusted content from the public internet. Because users routinely navigate to arbitrary public websites, the attack surface is considered likely to be exposed to external content during normal usage.

Out-of-bounds Write

Google Chrome

before 152.0.7977.65

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves a flaw in ANGLE, a component used in Google Chrome, which could allow an attacker to execute code outside the browser's safe environment. This is possible through a malicious webpage, and has been rated as having critical severity.

  • Flaw lets attackers run code outside the browser.
  • Critical severity means significant potential impact.
  • Confirm if Chrome is deployed and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could begin by creating a malicious HTML page. This page would then need to be accessed by a user. When the user visits this crafted page, it could trigger a flaw in the ANGLE component of Google Chrome. This flaw, an out-of-bounds write, could allow an attacker to execute code beyond the browser's security sandbox.

  • Requires user to visit a malicious webpage.
  • Triggered by loading a crafted HTML page.
  • Risk of arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could execute arbitrary code outside the sandbox by tricking a user into visiting a malicious HTML page, when supported by the advisory. This could lead to the compromise of system data and user data.

  • Arbitrary code execution outside sandbox.
  • Remote attacker via crafted HTML page.
  • System and user data compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's ANGLE component allows for remote code execution via a crafted HTML page. Ownership likely falls to the browser/endpoint security team, with initial triage focused on identifying and assessing the risk of affected Chrome instances, particularly those exposed to external web content. Coordination with the vendor for patching or mitigation strategies will be necessary.

  • Identify affected Chrome instances.
  • Verify external reachability and business criticality.
  • Coordinate vendor patch deployment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the ANGLE component in Google Chrome?

ANGLE is an abstraction layer that translates graphics instructions into formats understood by your computer's hardware. It allows Chrome to display complex web graphics, like 3D games or visual interfaces, consistently across different operating systems and graphics cards. Because it sits between web content and the underlying system, it is a critical piece of the browser's architecture.

What does an out-of-bounds write mean in CVE-2026-79131?

This vulnerability, classified as CWE-787, occurs when software writes data past the intended memory buffer limits. In the context of this CVE, the ANGLE component fails to properly check memory boundaries when processing content. An attacker can exploit this oversight to write malicious instructions into memory areas that should be off-limits, effectively breaking out of the browser's security sandbox.

How is this Chrome vulnerability triggered?

The flaw is triggered when a user navigates to a specifically crafted HTML page designed to exploit the graphics processing error. It does not trigger simply by having the browser installed or running; it requires the active rendering of malicious content provided by the attacker. Browsing trusted, static websites does not activate this specific memory write error.

Why should I care about this if I use Chrome internally?

Halo Surface Signal indicates that because Chrome is fundamentally designed to process untrusted content from the public internet, any instance of the browser is effectively exposed. Even if you primarily use Chrome for internal tools, users often navigate between internal resources and public sites, meaning the threat remains relevant whenever the browser interacts with external data.

Is updating Chrome the first step to address CVE-2026-79131?

Yes, verifying that your Chrome instances are updated to version 152.0.7977.65 or later is the primary defensive measure. Since the vulnerability is fixed by the vendor in this release, your immediate focus should be on auditing your environment to locate outdated versions and ensuring the latest security update is deployed to all managed systems.

References