Heap Buffer Overflow in WebRTC in Google Chrome on Windows
CVE-2026-12466 is a high-severity heap buffer overflow in the WebRTC component of Google Chrome affecting Windows versions prior to 149.0.7827.155. According to the provided content, the flaw can be triggered by a remote attacker via a crafted HTML page, leading to memory corruption in the browser process. The advisory does not provide the specific vulnerable function or code path, but it explicitly identifies the bug class as a heap-based buffer overflow in WebRTC and states that successful exploitation can result in arbitrary code execution.
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
6 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.
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.