High

Integer overflow in Google Chrome WebML

IdentifiersCVE-2026-3914CWE-472· External Control of…

CVE-2026-3914 is a high-severity integer overflow vulnerability in the WebML component/API of Google Chrome affecting versions prior to 146.0.7680.71. According to the provided content, a remote attacker can trigger the flaw by causing a target to load a crafted HTML page. Successful triggering can lead to heap corruption in the browser process. The available information does not identify the specific vulnerable function or code path within WebML, but the issue is characterized as an integer overflow that results in memory corruption during processing of malicious web content.

For your environment

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.

Start free trial

ANALYST BRIEF

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.

Successful exploitation can cause heap corruption in Chrome and may enable further memory-corruption outcomes, including browser process compromise. The provided CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates potential for high impact to confidentiality, integrity, and availability. The supporting content states that unpatched Chrome flaws in this release could allow arbitrary code execution, system compromise, or denial-of-service conditions, but for CVE-2026-3914 specifically the confirmed impact in the provided material is heap corruption via crafted HTML content.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and web content, especially arbitrary or attacker-controlled HTML pages, since exploitation requires a victim to visit a crafted page. Use browser update enforcement through enterprise management where available, restrict execution contexts for high-risk browsing, and prioritize rapid rollout of the Chrome stable update. These are temporary risk-reduction measures only; vendor patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.71 or later. The provided content states the vulnerability affects Chrome versions prior to 146.0.7680.71 and that Google addressed it in the Chrome 146 stable channel release. Apply the vendor update on all affected Windows, macOS, and Linux systems and restart the browser to ensure the patched version is active.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType

GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

5 SOURCESView more in app

cyber security newsNews

Mar 12, 2026

Chrome Security Update - Patch for 29 Vulnerabilities that Allows Remote Code Execution

High-severity vulnerability in Chrome’s WebML API (exact flaw type not specified in the content).

cvefeed high severityNews

Mar 11, 2026

CVE-2026-3914 - Google Chrome WebML Integer Overflow Heap Corruption

An integer overflow vulnerability in the WebML component of Google Chrome that can lead to heap corruption when processing a crafted HTML page, potentially enabling remote exploitation.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2