External risk intelligence

ANGLE Out-of-Bounds Write in Chrome Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79043

The vulnerability exists in a web browser, which is a client-side application designed to render untrusted content from the public internet. Because users routinely access the internet via this software, the attack surface is considered commonly reachable in standard deployment patterns.

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 advisory addresses a high-severity vulnerability in ANGLE, a component used in Google Chrome. An attacker could exploit this by directing users to a malicious webpage, potentially allowing them to execute unauthorized code. The primary concern is confirming if our systems utilize the affected browser versions.

  • Out-of-bounds write in ANGLE.
  • Matters for browser security, user protection.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by tricking a user into visiting a malicious webpage. This page contains crafted HTML that triggers an out-of-bounds write within the ANGLE graphics component of Google Chrome. If successful, this could allow the attacker to execute code outside the browser's security sandbox.

  • Attacker controls a web page.
  • User visits a malicious web page.
  • Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could exploit this vulnerability by tricking a user into visiting a malicious HTML page. This could potentially lead to the execution of arbitrary code outside the browser's sandbox.

  • Code execution outside the sandbox.
  • Malicious HTML page visited by user.
  • Potential for system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Addressing this vulnerability will likely involve coordination between platform teams managing browser deployments, security teams responsible for network and endpoint protection, and potentially vendor management if third-party software relies on the affected browser component. The initial practical step is to identify all systems running the affected browser, assess their exposure to untrusted web content, and confirm business criticality to prioritize remediation efforts.

  • Platform and security teams should own.
  • Verify browser reachability and criticality.
  • Plan coordinated remediation or mitigation.

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 calls from web applications into instructions your computer's graphics hardware understands. It helps Chrome display complex visual content and 3D graphics on web pages efficiently across different operating systems.

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

This weakness, categorized as CWE-787, occurs when software writes data past the end or before the beginning of its intended memory buffer. In this CVE, it allows an attacker to corrupt memory and potentially run their own unauthorized code instead of the browser's intended instructions.

How does an attacker trigger this Chrome vulnerability?

An attacker triggers this by convincing a user to navigate to a specifically crafted, malicious HTML page. Simply viewing legitimate or static websites does not trigger the bug; the browser must process the malicious instructions contained within the attacker-controlled page.

Why is this vulnerability considered relevant to my security?

According to Halo Surface Signal, this is a web browser issue, which is inherently designed to render untrusted content from the public internet. Because users routinely access the internet through this software, the risk of encountering a malicious page is high in standard deployments.

What steps should I take if I use Chrome?

Your first step is to inventory all systems running the affected browser versions to determine where the software is deployed. Once identified, prioritize these systems for updates, coordinating with your platform or IT teams to ensure the latest browser version is applied.

References