Loading vulnerability…
CVE-2026-11640 is a critical integer overflow vulnerability in libyuv affecting Google Chrome prior to 149.0.7827.103. According to the provided content, the flaw resides in the libyuv component and can be triggered via a crafted HTML page. The vulnerability is specifically described as exploitable by a remote attacker who has already compromised the renderer process, after which the integer overflow may be leveraged to escape Chrome’s sandbox. No vulnerable function or code path is identified in the provided material.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An integer overflow vulnerability in libyuv mentioned among the Chrome security fixes in this release.
A critical integer overflow vulnerability in Chrome's libyuv library.
Memory corruption vulnerability in libyuv referenced in the Chrome security update; noted as affecting not only Chromium-based browsers but also other software using the library such as Android, VLC, and Telegram.
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.