Loading vulnerability…
CVE-2026-17650 is a critical use-after-free vulnerability in the Compositing component of Google Chrome prior to version 151.0.7922.72. The flaw arises from improper lifetime management of memory in compositing-related code, creating a condition where freed memory can be accessed after release. According to the available information, exploitation requires an attacker to have already compromised the renderer process and then trigger the vulnerability using a crafted HTML page. In that post-renderer-compromise state, the bug can potentially be leveraged to cross Chrome’s security boundary and escape the sandbox.
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.
3 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.