Skip to main content
Mallory
Back to vulnerabilities
High

Heap Buffer Overflow in Chrome GPU Sandbox Escape on Android

IdentifiersCVE-2026-12010CWE-122· Heap-based Buffer Overflow

CVE-2026-12010 is a critical heap buffer overflow in the GPU component of Google Chrome on Android prior to version 149.0.7827.115. According to the provided content, a remote attacker could trigger the flaw via a crafted HTML page after first compromising the renderer process. The vulnerability is a memory-corruption issue in the GPU component and, because it is reachable in the context of a compromised renderer, it can potentially be used to cross Chrome's sandbox boundary. The available source material does not provide the specific vulnerable function or code path.

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.

Start free trial
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 an attacker who already has code execution or equivalent control in the renderer process to achieve a sandbox escape on affected Chrome for Android versions. This could enable further compromise of the browser environment beyond the renderer sandbox, with potential downstream impacts including arbitrary code execution in a more privileged process, broader access to browser or system resources, and possible full device compromise depending on chained exploitation and platform conditions.

Mitigation

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

No specific workaround is provided in the supplied content. Interim risk reduction is limited to reducing exposure until patching is complete: update Chrome promptly, restart the browser to ensure the new version is active, and apply standard browser hardening measures that reduce the likelihood of renderer compromise from malicious web content. Because exploitation requires a prior renderer compromise, reducing exposure to untrusted web content may lower risk, but patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Android to version 149.0.7827.115 or later. Where Chromium is consumed through downstream distributions, apply the corresponding vendor security update that incorporates the Chrome 149 fixes. Organizations should prioritize deployment because Google rated the issue critical.
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

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

ACTIVITY FEED

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

6 SOURCESView more in app
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.
Start free trial
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 activity2

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

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-12010
NVD
nvd.nist.gov/vuln/detail/CVE-2026-12010
MITRE CWE · CWE-122
Heap-based Buffer Overflow
Vendor Advisory
chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01962725236.html
Issue Tracking
issues.chromium.org/issues/517531647