External risk intelligence

Google Chrome for Android Dawn Use-After-Free Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-84333

The vulnerability exists in a client-side web browser application. Exploitation requires a user to visit a crafted web page, meaning the attack surface is not a public-facing service, appliance, or infrastructure component, but rather a client-side execution environment.

Use After Free

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 critical vulnerability discovered in the Dawn component of Google Chrome on Android. The flaw, categorized as a "use after free" issue, could potentially allow a remote attacker to execute malicious code outside the browser's security sandbox if a user visits a specially crafted web page. While the Chromium security team has rated this as High severity, its direct business impact relies on user interaction and the specific configurations of affected devices.

  • Vulnerability allows code execution on Android Chrome.
  • High risk if users visit malicious websites.
  • Confirm exposure; impact depends on user behavior.

Attack Path

How an attacker could exploit the issue

An attacker could lure a user to a malicious web page, which then exploits a flaw in Chrome's Dawn component. This could allow the attacker to run their own code on the user's device, bypassing security restrictions.

  • Entry: User visits a malicious page.
  • Trigger: Vulnerability in Dawn component.
  • Risk: Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a remote attacker to execute arbitrary code outside the sandbox on Android devices when supported by the advisory, by tricking a user into visiting a specifically crafted HTML page.

  • Arbitrary code execution in browser sandbox.
  • Attacker crafts a malicious HTML page.
  • Compromise of user device and data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome on Android impacts client-side execution environments. Initial triage should focus on identifying Chrome installations, assessing user exposure to malicious websites, and confirming business criticality. Platform or device management teams are likely responsible for managing browser updates, with coordination potentially needed with security teams to understand exposure and plan phased remediation.

  • Platform or device management teams.
  • Confirm user exposure to malicious websites.
  • Plan phased browser update rollout.

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 Dawn component in Google Chrome for Android?

Dawn is an open-source graphics library used by the Chromium engine to translate web-based graphics commands into instructions the device's hardware can process. It acts as a bridge, allowing web applications to utilize high-performance rendering capabilities, such as WebGPU, directly within the browser environment.

What does a use-after-free vulnerability mean for CVE-2026-84333?

This vulnerability, classified as CWE-416, happens when the browser continues to use a section of memory after it has been cleared or deleted. By manipulating this flaw, an attacker can trick the browser into referencing incorrect data or executing unauthorized instructions, effectively allowing them to bypass built-in security protections.

How is this vulnerability triggered by an attacker?

An attacker must entice a user to navigate to a specifically crafted HTML page designed to exploit the Dawn component's memory handling. Simply having the browser installed is not enough; the bug does not trigger through background processes or services, requiring active user interaction with the malicious web content to initiate the memory error.

How relevant is this CVE to my organization?

Halo Surface Signal indicates this is unlikely to impact infrastructure because it is a client-side vulnerability rather than a server-side service. The primary risk is to individual mobile devices where users might visit untrusted websites, making the threat surface specific to user behavior and web browsing activity rather than public-facing servers.

What steps should I take to address this Chrome vulnerability?

Prioritize updating Google Chrome on all Android devices to the version specified by the vendor to receive the patch. Because this is a client-side issue, coordinate with your mobile device management or platform teams to ensure that browser updates are deployed effectively to all endpoints running the affected software.

References