Loading vulnerability…
CVE-2026-6359 is a high-severity use-after-free vulnerability in the Video component of Google Chrome on Windows prior to version 147.0.7727.101. The flaw arises from video-handling code referencing memory after it has been freed, creating a dangling pointer condition that can lead to out-of-bounds memory access when the stale reference is dereferenced. A remote attacker can trigger the condition with a crafted HTML page, but successful exploitation requires that the attacker has already compromised the renderer process. The vulnerability is therefore best understood as a post-renderer-compromise memory-safety flaw that may be useful in a multi-stage browser exploit chain.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity use-after-free vulnerability in the Video component of Google Chrome on Windows that could allow a remote attacker, after compromising the renderer process, to perform out-of-bounds memory access via a crafted HTML page.
A high-severity use-after-free vulnerability in Video in Google Chrome.
A high-severity use-after-free vulnerability in the Video subsystem of Google Chrome that can enable out-of-bounds memory access via a crafted HTML page, but requires prior compromise of the renderer process and is therefore most likely useful as part of an exploit chain.
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.