Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds Read in Google Chrome WebML

IdentifiersCVE-2026-3915CWE-125

CVE-2026-3915 is a high-severity heap buffer overflow in the WebML component of Google Chrome prior to version 146.0.7680.71. According to the provided description, the flaw can be triggered by a crafted HTML page and results in an out-of-bounds memory read. The issue affects Chrome’s handling of WebML content and arises from improper bounds handling in heap memory, allowing memory to be read past the intended buffer boundary.

Share:
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.

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 allows a remote attacker to trigger an out-of-bounds read in the browser process by luring a target to a maliciously crafted web page. This can expose process memory contents and may cause browser instability or crashes. The provided content does not state that this specific CVE leads to code execution, so that should not be asserted based on the available information.

Mitigation

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

Until patching is completed, reduce exposure by limiting use of untrusted websites and untrusted HTML content in Chrome. Apply Chrome updates promptly through the browser’s update mechanism and restart the browser so the fix takes effect. Standard browser hardening and restricting access to potentially malicious web content may reduce likelihood of exploitation, but no complete mitigation short of updating is provided in the available content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.71 or later on Linux, or 146.0.7680.71/72 or later on Windows and macOS, as referenced in the provided content. Applying the vendor update is the primary remediation.
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.

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.
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 activity3

Community discussion across Reddit, Mastodon, and other social sources.