CVE-2026-12447 is a high-severity heap buffer overflow vulnerability in the WebRTC component of Google Chrome prior to version 149.0.7827.155. The flaw can be triggered by a remote attacker through a crafted HTML page, causing memory corruption in WebRTC and enabling arbitrary code execution within the browser's sandboxed renderer context. The issue affects Chromium-based browsers that incorporated the vulnerable Chromium codebase, including Google Chrome and Microsoft Edge builds based on affected versions.
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.
7 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 WebRTC component.
A high-severity heap buffer overflow vulnerability in Chrome WebRTC.
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.