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

Sandbox escape use-after-free in Google Chrome Viz

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

CVE-2026-6309 is a high-severity use-after-free vulnerability in the Viz component of Google Chrome affecting versions prior to 147.0.7727.101. The flaw is caused by improper object lifetime management that can leave a dangling pointer after memory has been freed. According to the provided content, a remote attacker who has already compromised a renderer process can trigger the bug via a crafted HTML page and potentially leverage the memory corruption in Viz to escape Chrome’s renderer sandbox. Viz is a privileged compositor component used for compositing and presentation, so corruption in this component can cross the security boundary between a sandboxed renderer and more privileged browser-side functionality.

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 allow an attacker who already has code execution in a compromised renderer process to break out of Chrome’s sandbox. Because the issue affects the privileged Viz component, exploitation may enable execution control beyond the renderer security boundary, with high impact to confidentiality, integrity, and availability. In practical terms, this can turn an initial renderer compromise into broader browser-process or similarly privileged compromise, enabling follow-on actions such as data access, arbitrary code execution in a more privileged context, or destabilization of the browser.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted web content, isolating high-risk browsing activity, and applying enterprise controls that restrict access to attacker-controlled sites. Because exploitation requires a prior renderer compromise and crafted web content, temporary mitigations include disabling or minimizing risky browsing workflows and ensuring additional browser hardening and OS-level sandbox protections remain enabled. However, no complete mitigation is provided in the content; patching is the definitive fix.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 147.0.7727.101 or later. The provided content states that fixed versions include 147.0.7727.101/102 for Windows and macOS, and 147.0.7727.101 for Linux and Android. Downstream Chromium-based browsers should also be updated once they incorporate the upstream Chromium fix.
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 activity3

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