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 WindowDialog sandbox escape

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

CVE-2026-3924 is a use-after-free vulnerability in the WindowDialog component of Google Chrome. According to the provided content, affected versions are Chrome prior to 146.0.7680.71. The flaw can be triggered via a crafted HTML page and, in the stated attack scenario, allows a remote attacker who has already compromised the renderer process to potentially escape Chrome’s sandbox. The issue is classified by Chromium as High severity.

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 could allow an attacker to break out of the renderer sandbox and execute actions outside the intended browser isolation boundary. In practical terms, this can enable elevation from a compromised renderer process to broader access on the host through a sandbox escape, increasing the likelihood of full browser compromise and subsequent system impact depending on post-escape capabilities.

Mitigation

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

Apply the vendor update as soon as possible. Until patching is completed, reduce exposure by limiting use of untrusted web content and isolating high-risk browsing activity, since the described exploit path involves a crafted HTML page and a pre-existing renderer compromise. Because Google is restricting detailed technical disclosure until users update, prompt patching is the primary mitigation supported by the provided content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.71 or later on affected platforms. The provided content indicates that Chrome 146 stable contains the fix, with 146.0.7680.71 listed for Linux and 146.0.7680.71/72 for Windows and macOS. A browser restart is required after updating to apply the 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.