Loading vulnerability…
CVE-2026-15767 is a high-severity heap buffer overflow in libyuv, the image and video format conversion library used by Google Chrome. The vulnerability affects Google Chrome on Windows prior to version 150.0.7871.125. A remote attacker can trigger the flaw by causing Chrome to process a crafted video file, leading to out-of-bounds heap memory writes during libyuv handling. Successful exploitation can result in arbitrary code execution within the Chrome 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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity heap buffer overflow vulnerability in Chrome's libyuv component used for image and video format conversion.
A high-severity heap buffer overflow vulnerability in Chrome's libyuv component.
A heap buffer overflow vulnerability in libyuv affecting Google Chrome on Windows prior to version 150.0.7871.125 that could allow remote code execution inside the sandbox via a crafted video file.
A high-severity heap buffer overflow vulnerability in Chrome's libyuv component.
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.