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

Out-of-bounds write in Chrome WebGPU on Android

IdentifiersCVE-2025-12725CWE-787

CVE-2025-12725 is a high-severity memory-safety vulnerability in Google Chrome’s WebGPU component on Android prior to version 142.0.7444.137. The provided content describes the issue as an out-of-bounds read in WebGPU that allows a remote attacker to trigger an out-of-bounds memory write via a crafted HTML page; supporting summaries consistently characterize the flaw as an out-of-bounds write in the WebGPU interface. In practical terms, the vulnerability can be reached through malicious web content rendered by Chrome, leading to memory corruption in the browser process when WebGPU-related operations are handled incorrectly.

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 can cause out-of-bounds memory writes, resulting in memory corruption. The likely security impact includes browser crashes, data corruption, and potentially arbitrary code execution in the context of the affected Chrome process on Android. Because the attack vector is a crafted HTML page, this is a remote client-side attack requiring only that a target load attacker-controlled web content.

Mitigation

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

If immediate patching is not possible, reduce exposure by avoiding untrusted or suspicious websites and limiting browsing to trusted content. Where administratively feasible, disable or restrict access to WebGPU functionality until the browser is updated. Enabling automatic browser updates can reduce the patch window for this and similar browser vulnerabilities.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Android to version 142.0.7444.137 or later. The content also notes Android fixed builds at 142.0.7444.138 or later as receiving the same security fixes. Applying the vendor update is the primary remediation.
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.

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 activity11

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