Use-after-free in Google Chrome Video on Windows
CVE-2026-6359 is a high-severity use-after-free vulnerability in the Video component of Google Chrome on Windows prior to 147.0.7727.101. The flaw stems 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. According to the provided content, exploitation is possible via a crafted HTML page, but only after the attacker has already compromised the Chrome renderer process. The issue is tracked in Chromium as issue 490251701.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 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.
The version that knows your environment.
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.