External risk intelligence

Google Chrome on Android could allow an external attacker to gain unauthorized device access.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-6920

An external attacker could exploit a flaw in Google Chrome on Android by tricking a user into visiting a malicious website. This allows them to bypass security protections, potentially leading to full device control and unauthorized access to sensitive user information.

1Halo Surface Signal

Out-of-bounds Read

Google Chrome

before 147.0.7727.116

External exposure likelihood

Halo Surface Signal score for CVE-2026-6920

This vulnerability affects Google Chrome on Android, which is client-side software. The browser acts as a user-facing client rather than a public-facing service, gateway, or network-reachable management portal. Since the application is not an internet-facing service, it is primarily local to the device and does not have the typical public network exposure of an edge-facing system.

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Google Chrome on Android could allow an attacker to escape the browser's security sandbox. This means a malicious webpage could potentially access or control more of your device than it should.

  • A malicious website could be dangerous.
  • Users of Chrome on Android are affected.
  • This could lead to unauthorized access to device functions.

Attack Path

How an attacker could exploit the issue

An attacker can leverage this flaw by tricking a user into visiting a malicious webpage. This could lead to the attacker gaining elevated privileges within the user's device, potentially allowing them to escape the browser's sandbox and execute arbitrary code.

  • Compromise renderer process.
  • User visits crafted HTML page.
  • Sandbox escape to achieve code execution.

Live Threat

Current exploitation, exposure, and threat context

Attackers will likely find this vulnerability attractive due to its potential for sandbox escape within a widely used application, enabling further compromise of the user's device. The described out-of-bounds read in the GPU component, exploitable via a crafted HTML page, presents a direct path for a remote attacker to gain elevated privileges.

  • Requires user interaction.
  • No KEV listing.
  • Exploited through browser.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams should prioritize updating Google Chrome on Android to the latest patched version. If immediate patching is not feasible, focus on monitoring for signs of exploitation or unexpected browser behavior on affected devices. The ability for a remote attacker to achieve a sandbox escape via a crafted HTML page necessitates prompt action.

  • Update Chrome to version 147.0.7727.117.
  • Monitor for malicious activity.
  • Isolate affected devices if needed.

Frequently asked questions

What is Google Chrome on Android and what is it used for?

Google Chrome on Android is a web browser application used on Android mobile devices. It allows users to access and navigate websites, stream media, and interact with web applications, serving as the primary interface for many online activities on a phone or tablet.

What type of vulnerability is CVE-2026-6920 in Chrome on Android?

CVE-2026-6920 is an out-of-bounds read vulnerability in the GPU component of Google Chrome on Android. This weakness, categorized as CWE-125, means the software tried to access memory it shouldn't have, which could lead to unexpected behavior or data corruption.

How can an attacker trigger the vulnerability in Chrome on Android?

An attacker can trigger this vulnerability by successfully compromising the renderer process and then presenting a specially crafted HTML page to the user. Visiting this malicious page through Chrome on Android could allow the attacker to bypass security restrictions.

Who should be concerned about this Chrome on Android vulnerability?

Users and organizations running Google Chrome on Android devices should be concerned. This is because the vulnerability, while client-side, could potentially lead to a sandbox escape, allowing unauthorized access to device functions, even though the Halo Surface Signal indicates it's very unlikely to be an internet-facing threat.

What is the first step to address CVE-2026-6920 on Android devices?

The immediate first step for anyone running this technology is to update Google Chrome on their Android devices to version 147.0.7727.117 or later. This update contains the necessary patches to fix the vulnerability.

References