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

Sandbox escape in Google Chrome Accessibility on Windows

IdentifiersCVE-2026-6311CWE-457· Use of Uninitialized Variable

CVE-2026-6311 is a high-severity use of uninitialized variable vulnerability in the Accessibility component of Google Chrome on Windows. It affects Chrome versions prior to 147.0.7727.101. According to the provided content, a remote attacker who has already compromised the sandboxed renderer process can trigger the flaw via a crafted HTML page and potentially escape Chrome's sandbox. The root cause is classified as CWE-457. Public technical detail about the exact vulnerable code path or function is currently not available because the associated Chromium issue is restricted.

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 cross Chrome's renderer sandbox boundary on Windows. The provided content indicates high impact to confidentiality, integrity, and availability, consistent with the CVSS v3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. In practical terms, an attacker who already achieved renderer compromise could potentially execute code or otherwise gain control outside the sandbox, enabling broader compromise of the underlying Windows system.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and content, restricting browser use in high-risk workflows, and applying standard browser hardening and endpoint controls to make initial renderer compromise more difficult. Because exploitation requires a prior renderer compromise plus user interaction with crafted web content, mitigations that reduce exposure to malicious pages and block exploit chains may help, but no complete mitigation is provided in the content aside from updating.

Remediation

Patch, then assume compromise.

Update Google Chrome on Windows to version 147.0.7727.101 or later. The provided content also references 147.0.7727.102 as an advised updated version for some desktop channels. Applying the vendor-provided stable channel 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 activity3

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