External risk intelligence

ANGLE Out-of-Bounds Read in Google Chrome for Android Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-131057

This vulnerability affects the ANGLE graphics component within the Google Chrome browser on Android. Exploitation requires a user to navigate to a crafted HTML page. As a client-side browser component, it is not an internet-facing service, gateway, or management surface, but rather a local application component that requires user interaction to reach.

Out-of-bounds Read

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

This advisory describes a security vulnerability in the ANGLE graphics component of Google Chrome on Android. The issue, classified as High severity by Chromium, could allow a remote attacker to execute code outside the browser's secure environment through a specially crafted webpage. The main concern is confirming the relevance and exposure of this vulnerability to our specific Android user base.

  • Reading beyond memory limits.
  • Could allow code execution.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious website containing specially crafted HTML. This page would interact with the ANGLE component within the Chrome browser on Android, potentially leading to code execution outside the browser's security boundaries.

  • User visits a malicious page.
  • Crafted HTML triggers an out-of-bounds read.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

An out-of-bounds read in ANGLE, a component within Google Chrome on Android, could allow a remote attacker to execute arbitrary code outside the sandbox. This could occur when a user visits a specially crafted HTML page, potentially impacting the confidentiality, integrity, and availability of the user's device.

  • User's device data and system functions.
  • Visiting a malicious web page.
  • Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the ANGLE component within Chrome on Android, and exploitation requires user interaction with a malicious HTML page. Responsibility likely falls to teams managing end-user device security and application lifecycle, such as mobile platform or endpoint security teams, in coordination with any vendor management for Chrome updates. The initial step is to identify affected Android devices, assess exposure through user browsing habits, and plan for timely browser updates, potentially involving user education or mobile device management (MDM) policies.

  • Own by endpoint security and platform teams.
  • Verify user exposure to malicious pages.
  • Plan for timely browser updates.

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

ANGLE is a graphics engine abstraction layer used by Chrome to translate graphics calls into formats supported by the underlying Android hardware. It acts as a translator between the browser's web content and the device's graphics processing unit (GPU), ensuring consistent rendering of web-based visuals and animations.

What does an out-of-bounds read mean for CVE-2026-131057?

This vulnerability, classified as CWE-125, occurs when the software reads data past the end of a designated memory buffer. In this context, it allows an attacker to access sensitive memory areas outside of Chrome's sandbox, potentially enabling the execution of arbitrary code on the Android device.

How is this Chrome vulnerability triggered?

An attacker must lure a user into visiting a malicious webpage containing specifically crafted HTML content designed to interact with the ANGLE component. Simply having the browser installed or running in the background does not trigger the flaw; it requires active engagement with the deceptive page.

Is my organization at risk from this Chrome vulnerability?

According to Halo Surface Signal, this vulnerability affects a client-side browser component rather than an internet-facing server. Risk is localized to individual Android devices where users navigate to malicious content, making it less of a traditional network-perimeter exposure.

How should I respond to CVE-2026-131057?

The primary defense is ensuring Chrome for Android is updated to version 158.0.8127.36 or later, which contains the fix. Organizations should focus on identifying devices running older versions and using mobile management policies to enforce or encourage these browser updates.

References