External risk intelligence

Chrome ANGLE Code Execution via Crafted HTML

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113252

The vulnerability exists within the ANGLE graphics engine component of the Google Chrome web browser. While it requires a user to interact with a crafted HTML page, the component itself is client-side software rather than a public-facing network service, appliance, or gateway. Public internet exposure is uncommon as this is a local client application environment.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in the ANGLE component of Google Chrome on Windows, potentially allowing attackers to execute code outside the browser's safety features. This could occur if a user visits a malicious webpage. The main concern at this time is to confirm if this specific technology is relevant to our environment.

  • Input validation flaw in Chrome's graphics engine.
  • Could allow remote code execution if exploited.
  • Confirm relevance and exposure to our environment.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage, which then interacts with the ANGLE component in Google Chrome. If successful, this could allow the attacker to execute code with elevated privileges outside the browser's security sandbox.

  • Requires a user to visit a malicious page.
  • Triggered by rendering a crafted HTML page.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a remote attacker could execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page within Google Chrome on Windows. This could affect the integrity and confidentiality of system data.

  • Arbitrary code execution outside sandbox.
  • User visits crafted HTML page.
  • System compromise may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in ANGLE, a component of Google Chrome, requires a user to visit a malicious HTML page to be exploited. Therefore, the primary responsibility lies with teams managing end-user devices and browser deployments, likely endpoint management or security operations, to identify and mitigate the risk. The initial step is to inventory Chrome installations, confirm exposure on user endpoints, and then coordinate remediation efforts, potentially involving user communication or targeted updates.

  • Endpoint management and security operations own this.
  • Verify Chrome installations on endpoints.
  • Plan targeted updates and user advisories.

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 a graphics engine abstraction layer used by Chrome. It translates high-level graphics calls from web content into the specific commands required by your computer's graphics hardware (like DirectX on Windows). By serving as this bridge, it enables complex 3D graphics and animations to run smoothly within your browser.

What does CWE-20 mean regarding CVE-2026-113252?

CWE-20 refers to improper input validation. In the context of this vulnerability, it means the ANGLE component fails to correctly check or sanitize data provided by a website before processing it. Because of this oversight, a maliciously crafted HTML page can send unexpected instructions that cause the engine to misbehave, potentially leading to unauthorized code execution.

How is this vulnerability triggered?

The flaw is triggered when a user navigates to a specifically crafted HTML page using an affected version of Chrome on Windows. The malicious content exploits the input validation weakness during the rendering process. Simply having the browser installed is not enough; the vulnerability does not trigger if the user does not visit the malicious site or interact with the compromised content.

Is this a risk for my servers?

Halo Surface Signal indicates that while this is a browser-based flaw, it is generally unlikely to affect servers because Chrome is a client-side application. The risk is primarily focused on endpoint devices where users actively browse the internet. Your exposure is highest on workstations where employees perform daily tasks rather than on infrastructure components or public-facing network services.

How do I respond to CVE-2026-113252?

Your first step is to inventory your environment to identify systems running older, vulnerable versions of Google Chrome on Windows. Once identified, prioritize updating these installations to version 156.0.8078.47 or later. Since this vulnerability requires user interaction with a web page, coordinating with endpoint management teams to ensure a smooth, enterprise-wide update is the most effective way to secure your environment.

References