Heap Buffer Overflow in Google Chrome WebML
CVE-2026-3913 is a critical heap buffer overflow vulnerability in the WebML component of Google Chrome. It affects Chrome versions prior to 146.0.7680.71. According to the provided content, a remote attacker can trigger heap corruption by causing a target to load a crafted HTML page. The issue is classified as Chromium security severity Critical and is associated with CWE-122. The available reporting indicates the flaw may be exploitable for remote code execution, although Google has limited disclosure of technical details pending broad patch adoption.
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
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical-severity heap buffer overflow (memory corruption) in Chrome’s WebML component that could potentially lead to remote code execution when a user visits a malicious web page.
A critical heap buffer overflow (CWE-122) in Chrome's WebML component that can be triggered via a crafted HTML page, potentially leading to heap corruption and high-impact compromise.
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.