External risk intelligence

Google Chrome Android Privilege Elevation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-121234

This vulnerability affects the Contacts component within the Google Chrome browser on Android. Browser components are client-side software; they are not public-facing services, gateways, or APIs. Exploitation requires a user to interact with a crafted HTML page within the local browser environment, making it a client-side issue rather than a public-facing network service.

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 details a privilege elevation vulnerability within the Contacts feature of Google Chrome on Android. The issue could allow a remote attacker to execute arbitrary code by luring a user to a malicious HTML page. While the technical severity is high, its impact is primarily confined to the user's device rather than broader organizational systems.

  • A browser flaw can let code run outside its safe zone.
  • Protects users from malicious web page code execution.
  • Confirm if employee devices are affected by this browser issue.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious website, which would then interact with the Chrome browser on an Android device. This interaction could lead to code execution outside of the browser's secure sandbox.

  • Entry condition: User visits a malicious website.
  • Trigger point: Crafted HTML page interacts with Contacts.
  • Resulting risk: Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page. This could affect sensitive information or system behavior within the user's local browser environment.

  • User data in the browser.
  • Malicious HTML page interaction.
  • Potential code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects the Contacts component of Google Chrome on Android. Exploitation requires user interaction with a malicious HTML page within the browser. Therefore, the primary responsibility lies with teams managing user endpoint devices and browser deployments, potentially including IT support and mobile device management teams. The first practical step is to identify Android devices running affected Chrome versions and assess the risk based on user activity and the potential for exposure to malicious content.

  • Mobile device and endpoint management teams should own this.
  • Verify affected Android devices and Chrome versions.
  • Plan targeted user guidance and 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 Contacts component in Google Chrome on Android?

The Contacts component is a specific feature within the Google Chrome browser on Android devices. It enables the browser to interface with the mobile device's address book or contact management system, allowing users to share or interact with contact data through web-based activities.

What does CWE-250 privilege elevation mean in CVE-2026-121234?

CWE-250 refers to Execution with Unnecessary Privileges. In this context, it means the browser component incorrectly performs actions with higher authority than it should have. This flaw allows malicious code to break out of the browser's secure 'sandbox'—a safety wall designed to contain web content—and run with deeper access to the Android device.

How does an attacker trigger this vulnerability?

An attacker triggers this by luring a user to visit a specifically crafted malicious HTML page. This bug is not triggered by normal browsing of reputable websites; it requires the user to interact with the malicious content, which then exploits the Contacts component to initiate the unauthorized code execution.

Why is this considered a client-side issue?

According to Halo Surface Signal, this vulnerability is not a public-facing service, gateway, or API. It exists entirely on the individual user's device. Because the exploitation relies on a user visiting a site within their local browser environment, it does not present a direct network-based attack surface against corporate server infrastructure.

What should I do if I manage Android devices?

Your first step is to inventory your Android fleet to identify devices running Chrome versions older than 157.0.8103.38. Coordinate with your mobile device management or IT support teams to ensure these devices receive the necessary browser updates, and consider providing guidance to users about avoiding suspicious web links.

References