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

Heap buffer overflow in Chrome WebGL

IdentifiersCVE-2026-4675CWE-122· Heap-based Buffer Overflow

CVE-2026-4675 is a high-severity heap buffer overflow in the WebGL component of Google Chrome. It affects Chrome versions prior to 146.0.7680.165. According to the provided content, the flaw can be triggered when a target visits a crafted HTML page, leading to an out-of-bounds memory read in the browser process handling WebGL content. Chromium classified the issue as High severity, and the CVE record maps it to CWE-122.

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 cause out-of-bounds memory access in Chrome via malicious web content. The provided content specifically states out-of-bounds memory read, which can result in information disclosure and browser instability or crash. Supporting context also notes that Chrome memory corruption flaws of this class may contribute to broader exploit chains and, depending on surrounding conditions, may help enable more serious outcomes such as code execution or host compromise, but the specific confirmed impact here is an out-of-bounds read via WebGL.

Mitigation

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

Apply the vendor patch as soon as possible and ensure browser restart after update so the fix takes effect. Until patching is complete, reduce exposure to untrusted web content, restrict access to arbitrary websites where feasible, and use enterprise patch management to accelerate deployment across managed systems. The content does not provide a component-specific workaround short of updating.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 146.0.7680.165 or later. The provided content indicates that versions prior to 146.0.7680.165 are vulnerable. Because Chromium-based browsers may inherit the same vulnerable code, corresponding vendor updates should also be applied where relevant.
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 activity5

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