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 flaw is described as an out-of-bounds write, also characterized in related references as a heap buffer overflow, indicating improper bounds handling during GPU-related memory operations. A remote attacker could trigger the issue using a crafted HTML page after first compromising the renderer process. Successful exploitation could allow the attacker to cross the browser security boundary and potentially escape Chrome's sandbox.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds write vulnerability in the GPU component of Google Chrome on Android that could allow a remote attacker, after compromising the renderer process, to potentially escape the sandbox via a crafted HTML page.
A high-severity heap buffer overflow vulnerability in Chrome GPU.
A high-severity heap buffer overflow vulnerability in Chrome GPU.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.