High

Heap buffer overflow in WebRTC in Google Chrome

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

CVE-2026-4463 is a high-severity heap buffer overflow in the WebRTC component of Google Chrome. According to the provided content, affected versions are Google Chrome prior to 146.0.7680.153. The flaw can be triggered by a remote attacker via a crafted HTML page, leading to heap corruption in the browser process while handling WebRTC-related content. No vulnerable function or deeper root-cause details are provided in the supplied material.

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 could allow a remote attacker to corrupt heap memory in Chrome via malicious web content. Based on the supplied context for this Chrome release, memory corruption vulnerabilities of this class may result in arbitrary code execution, denial of service through browser crash, or potentially information disclosure, depending on exploitability and runtime conditions. The provided content does not confirm observed in-the-wild exploitation for this specific CVE.

Mitigation

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

Apply the vendor update as the primary mitigation. Until patching is completed, reduce exposure by limiting access to untrusted or attacker-controlled websites and web content, and consider restricting or disabling unnecessary WebRTC use where operationally feasible. Because this issue is triggered through crafted HTML content, standard browser hardening and rapid update deployment are the most relevant interim measures. The provided content does not include any vendor-specific workaround beyond updating.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later. The supplied content indicates that 146.0.7680.153 and 146.0.7680.154 were released for Windows and macOS, and 146.0.7680.153 for Linux, with this vulnerability fixed in versions at or above 146.0.7680.153.

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

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

7 SOURCESView more in app

cyber security newsNews

Mar 21, 2026

Chrome Security Update Patches 26 Vulnerabilities that Enable Attackers to Execute Malicious Code Remotely

A high-severity heap buffer overflow vulnerability in Chrome's WebRTC component.

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 activity4