Loading vulnerability…
CVE-2026-3924 is a high-severity use-after-free vulnerability in the WindowDialog component of Google Chrome prior to version 146.0.7680.71. The flaw arises from incorrect lifetime management of memory in WindowDialog, creating a condition where freed memory can be accessed after release. According to the available information, exploitation is possible by a remote attacker who has already compromised the renderer process, and can be triggered in the context of a crafted HTML page. The vulnerability is notable because it may enable a sandbox escape from the compromised renderer, crossing Chrome's security boundary between renderer and more privileged browser contexts.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.