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

Use-after-free in WebRTC in Google Chrome

IdentifiersCVE-2026-4446CWE-416· Use After Free

CVE-2026-4446 is a high-severity use-after-free vulnerability 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 a use-after-free condition and resulting heap corruption in the browser process. The available information does not identify the specific vulnerable function or code path within WebRTC.

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 could allow a remote attacker to corrupt heap memory in Chrome by convincing a user to visit a maliciously crafted webpage. Based on the provided context for this Chrome release, memory corruption vulnerabilities in components such as WebRTC may enable arbitrary code execution, and could also result in denial of service or information disclosure depending on exploitability and runtime conditions.

Mitigation

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

Until patching is completed, reduce exposure by restricting use of untrusted websites and web content, especially in contexts where WebRTC is enabled. Standard browser hardening measures such as minimizing unnecessary browser features, isolating high-risk browsing activity, and enforcing rapid browser update deployment may reduce risk. The provided content does not include a vendor-specified workaround for disabling the vulnerable code path.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later. The provided content indicates that Google fixed this issue in Chrome 146.0.7680.153, with 146.0.7680.153/.154 released for Windows and macOS and 146.0.7680.153 for Linux. Apply the corresponding Chromium-based browser vendor updates where applicable.
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.