Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Out-of-bounds write in Chrome GPU on Android

IdentifiersCVE-2026-9872CWE-787· Out-of-bounds Write

CVE-2026-9872 is a critical out-of-bounds write vulnerability in the GPU component/process of Google Chrome on Android prior to version 148.0.7778.216. According to the provided content, the flaw can be triggered remotely via a crafted HTML page. The issue is a memory corruption bug in Chrome’s graphics/GPU subsystem and is described by Google as potentially enabling a sandbox escape. The available source material does not provide the exact vulnerable function or code path, and Google reportedly restricted detailed technical disclosure pending patch adoption.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could allow a remote attacker to corrupt memory in the Chrome GPU process and potentially achieve a sandbox escape. The provided content also states that exploitation of this class of Chrome vulnerabilities may lead to remote code execution or data corruption, depending on exploit chain development and runtime conditions. No in-the-wild exploitation was reported at the time of disclosure in the supplied content.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is provided in the supplied content. If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and malicious HTML content, and prioritize rapid browser update deployment and restart so the patched version is active. However, the provided advisories indicate that upgrading is the recommended corrective action.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Android to version 148.0.7778.216 or later. More generally, deploy the vendor-fixed Chrome/Chromium builds referenced in the advisories and ensure managed environments are not affected by version drift. Because Google limited technical disclosure until users are patched, prompt upgrade is the primary remediation supported by the provided content.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
GoogleChromiumapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.