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 Graphite in Google Chrome

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

CVE-2026-6304 is a high-severity use-after-free vulnerability in the Graphite component of Google Chrome, specifically in Chrome’s Skia Graphite GPU rasterization backend. In affected versions prior to 147.0.7727.101, a freed object in the Graphite rasterization pipeline can be accessed after deallocation, creating a memory-safety flaw. Because Graphite operates in Chrome’s GPU process rather than the renderer process, successful exploitation can cross Chrome’s process trust boundary. According to the available vendor description, a remote attacker can trigger the issue with a crafted HTML page, but exploitation requires that the attacker has already compromised the renderer process through a separate vulnerability. The flaw was fixed in Chrome 147.0.7727.101/102 for Windows and macOS and 147.0.7727.101 for Linux and Android.

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 a sandbox escape from an already-compromised renderer process into the more privileged GPU process, potentially giving the attacker access beyond the renderer sandbox and into the underlying operating system context. The published CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) indicates high potential impact to confidentiality, integrity, and availability once the trust boundary is crossed.

Mitigation

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

Apply the vendor patch as the primary mitigation. Where immediate patching is not possible, reduce exposure by limiting use of vulnerable Chrome/Chromium builds, restricting execution of untrusted web content, and using defense-in-depth controls that make initial renderer compromise harder, since exploitation requires a separate renderer-process compromise first. Organizations should also prioritize updates for Chromium-based browsers that may have inherited the vulnerable Graphite backend.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to a fixed release. The available content indicates the vulnerability was addressed in Chrome 147.0.7727.101/102 for Windows and macOS, and 147.0.7727.101 for Linux and Android. Any Chrome version prior to 147.0.7727.101 should be considered vulnerable. Downstream Chromium-based browsers that incorporate the affected Graphite code should also be updated once vendor fixes are available.
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.