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

Use-after-free in Google Chrome WebGPU

IdentifiersCVE-2026-4678CWE-416· Use After Free

CVE-2026-4678 is a high-severity use-after-free vulnerability in the WebGPU component of Google Chrome. It affects Chrome versions prior to 146.0.7680.165. The flaw is triggered when a crafted HTML page causes Chrome to access memory after it has been freed within WebGPU processing, creating a memory corruption condition. According to the provided content, successful exploitation allows a remote attacker to execute arbitrary code inside the Chrome sandbox. Google/Chromium has restricted detailed technical information pending broad patch adoption.

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 result in arbitrary code execution within the Chrome renderer sandbox in the context of the targeted browsing session. The provided CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates high impact to confidentiality, integrity, and availability. The content specifically confirms code execution inside the sandbox; broader host compromise or sandbox escape is not established by the provided data alone.

Mitigation

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

Until patching is complete, reduce exposure by limiting access to untrusted or attacker-controlled websites and enforcing rapid browser update deployment through enterprise patch management. Because exploitation requires loading a crafted HTML page, standard browser hardening measures such as restricting risky browsing destinations and ensuring prompt browser restarts after update installation can reduce risk. However, mitigation is not a substitute for upgrading to a fixed Chrome version.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 146.0.7680.165 or later. The provided content states Google released fixes in Chrome 146.0.7680.164/165 for Windows and Mac and 146.0.7680.164 for Linux as part of the relevant security update rollout. Apply the latest vendor-provided stable build available for the affected platform and restart the browser so the fix takes effect.
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 activity8

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