External risk intelligence

ANGLE Protection Mechanism Failure in Chrome for Android Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-130910

This vulnerability is located within the ANGLE graphics engine component of a web browser (Google Chrome on Android). Exploitation requires a user to interact with a crafted HTML page within the browser environment. It is not an internet-facing service, gateway, or network appliance; it is client-side software requiring specific user-driven navigation.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security flaw in Google Chrome on Android could allow attackers to execute code outside the browser's protected area by tricking users into visiting a malicious web page. This could potentially impact the confidentiality, integrity, and availability of user data if exploited.

  • A browser flaw lets attackers break out of a sandbox.
  • It matters if users visit malicious websites.
  • Confirm relevance and exposure for Android Chrome users.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious HTML page. This page would leverage a weakness in how Google Chrome on Android handles graphics, allowing code to run outside of its normal security boundaries. If successful, this could lead to the execution of arbitrary code.

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

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could potentially execute arbitrary code outside the sandbox when a user visits a specially crafted HTML page in a vulnerable version of Google Chrome on Android. This could impact the confidentiality, integrity, and availability of the affected device.

  • System code and data.
  • Via a crafted HTML page.
  • Arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

To address this vulnerability, platform or application teams responsible for Google Chrome on Android deployments should initiate an inventory of affected assets. The primary focus will be identifying instances of the vulnerable browser, assessing their exposure through user interaction with malicious web content, and confirming business criticality before planning remediation.

  • Platform or application teams own remediation.
  • Verify user-facing browser instances.
  • Plan updates based on risk.

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 Google Chrome on Android?

It is a mobile web browser that uses the Chromium engine to render websites. This specific vulnerability involves ANGLE, a graphics abstraction layer within Chromium that translates various graphics API calls into formats the device's hardware can process. It helps ensure consistent rendering performance across different Android hardware configurations.

What does CWE-693 mean for CVE-2026-130910?

CWE-693 refers to Protection Mechanism Failure. In this context, it means the browser's internal security defenses—specifically the sandbox designed to isolate web content from the rest of the device—failed to prevent a malicious process from escaping its restricted environment. Because of this weakness, code that should be confined to the browser can potentially interact with the underlying operating system.

How is this vulnerability triggered?

An attacker must successfully induce a user to navigate to a specifically crafted HTML page using a vulnerable version of Chrome on Android. Simply having the browser installed or running in the background is not enough to trigger the bug. It requires an active session where the browser processes the malicious graphics instructions embedded in the webpage.

Is my device at risk based on Halo Surface Signal?

Halo Surface Signal indicates that this is very unlikely to be a widespread network-based threat because it requires direct user interaction with a malicious page. Since this is client-side software rather than an internet-facing gateway or server, the risk is tied specifically to user behavior and web navigation rather than automated network scanning.

When should I update my browser?

You should update to the patched version as soon as it becomes available through your app store or system update mechanism. Prioritize this update if you frequently browse sites outside of trusted domains, as the vulnerability relies on visiting malicious web content. Check your version against the release notes to confirm you are running 158.0.8127.36 or higher.

References