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

Sandbox escape via out-of-bounds write in Google Chrome GPU

IdentifiersCVE-2026-6314CWE-787· Out-of-bounds Write

CVE-2026-6314 is a high-severity out-of-bounds write vulnerability in the GPU component/process of Google Chrome. It affects Chrome versions prior to 147.0.7727.101, with fixed releases identified as 147.0.7727.101 for Linux and 147.0.7727.101/.102 for Windows and macOS. According to the provided content, a remote attacker can trigger the issue using a crafted HTML page, but exploitation is not single-stage: the attacker must first achieve compromise of the GPU process through a separate vulnerability or technique, then leverage the out-of-bounds write to corrupt memory in the GPU process and escape the sandbox. Publicly available material does not disclose the exact vulnerable function, buffer, or bounds-check failure, and Chromium issue details were restricted at disclosure time.

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 break out of Chrome’s GPU sandbox and transition a compromise of the GPU process into code execution or control in a broader system context. Because the vulnerability is an out-of-bounds write, the resulting memory corruption may enable arbitrary code execution, integrity compromise, sensitive data exposure, or process destabilization. The provided CVSS vector and supporting context indicate high confidentiality, integrity, and availability impact with changed scope, reflecting that exploitation crosses a security boundary rather than remaining confined to the compromised GPU process.

Mitigation

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

If immediate patching is not possible, reduce exposure to the GPU attack surface by manually disabling Chrome hardware acceleration, as noted in the provided content. This is only a temporary risk-reduction measure and not a substitute for patching. The content also notes there is no enterprise Group Policy available to centrally disable Chrome hardware acceleration. Additional practical mitigation is to limit exposure to untrusted web content until patched, since exploitation requires a crafted HTML page and user interaction.

Remediation

Patch, then assume compromise.

Update Google Chrome to a fixed version or later. The provided content identifies the patched versions as 147.0.7727.101 for Linux and 147.0.7727.101 or 147.0.7727.102 for Windows and macOS, depending on rollout channel/build. Downstream Chromium-based browsers should also be updated once they incorporate the upstream Chromium fix. Because technical details were restricted at disclosure, standard patch prioritization for sandbox-escape-class browser vulnerabilities is warranted.
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.