Skip to main content
Mallory
Back to vulnerabilities
High

Sandbox escape via GPU out-of-bounds write in Google Chrome on Android

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

CVE-2026-12030 is a high-severity memory corruption vulnerability in the GPU component of Google Chrome on Android prior to version 149.0.7827.115. The issue is described as an out-of-bounds write / heap buffer overflow in GPU processing. According to the provided content, a remote attacker could trigger the flaw using a crafted HTML page, but exploitation requires that the renderer process has already been compromised. In that post-compromise state, the GPU memory corruption bug could be leveraged to cross Chrome's security boundary and potentially escape the sandbox.

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 achieved renderer-process compromise to perform a sandbox escape on affected Chrome for Android builds. Because the CVSS vector indicates scope change and high impact to confidentiality, integrity, and availability, the likely consequence is execution or control outside the renderer sandbox with access to more privileged browser or system resources, potentially enabling arbitrary code execution, further compromise of the browser process, data access, or device-level impact depending on exploit chain specifics.

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, mitigation is limited to reducing exposure by updating as quickly as possible, restricting use of affected Chrome on Android versions prior to 149.0.7827.115, and minimizing access to untrusted web content. Because exploitation requires prior renderer compromise, broader browser hardening and reducing exposure to renderer-targeting 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. For downstream Chromium-based packages, apply the vendor security updates that incorporate the upstream fix; the provided Debian advisory lists chromium 149.0.7827.114-1~deb12u1 for bookworm and 149.0.7827.114-1~deb13u1 for trixie. Prioritize patching because the flaw is a high-severity sandbox-escape primitive in the GPU component.
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 activity3

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

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-12030
NVD
nvd.nist.gov/vuln/detail/CVE-2026-12030
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/518007423