CVE-2025-12725 is a high-severity memory-safety vulnerability in the WebGPU component of Google Chrome on Android prior to version 142.0.7444.137. The issue is described as involving WebGPU and is associated with out-of-bounds memory access, with available reporting indicating the security impact is an out-of-bounds write reachable through a crafted HTML page. Successful exploitation could corrupt adjacent memory during browser processing of attacker-controlled web content, creating conditions for browser instability and potential code execution within the Chrome process.
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.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical out-of-bounds write vulnerability in Chrome's WebGPU interface that could allow remote code execution by enabling attackers to overwrite system memory and execute arbitrary code.
High-severity out-of-bounds write vulnerability in Google Chrome’s WebGPU API that could potentially lead to crashes or arbitrary code execution.
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.