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

Heap Buffer Overflow in Google Chrome WebAudio

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

CVE-2026-4443 is a high-severity heap buffer overflow vulnerability in the WebAudio component of Google Chrome. According to the provided content, it affects Google Chrome prior to version 146.0.7680.153 and can be triggered by a remote attacker via a crafted HTML page. The flaw is a memory corruption issue in WebAudio that can lead to out-of-bounds writes or corruption of heap memory during processing of attacker-controlled web content. Google states that successful exploitation may allow arbitrary code execution inside the Chrome sandbox.

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, unauthenticated attacker to achieve arbitrary code execution within the Chrome renderer sandbox by convincing a user to visit a maliciously crafted webpage. As a heap memory corruption issue, it may also cause browser process instability or crashes, resulting in denial of service. Based on the provided information, code execution is limited to the sandboxed context; no sandbox escape is described.

Mitigation

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

Until patched versions can be deployed, reduce exposure by restricting use of untrusted websites and web content, especially attacker-controlled HTML pages. Standard browser hardening measures such as minimizing unnecessary browsing from sensitive environments, using application isolation, and enforcing rapid browser update policies may reduce risk. However, no specific mitigation short of updating is provided in the content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later. The provided content indicates that the issue is fixed in Chrome 146.0.7680.153, with Windows and macOS also receiving 146.0.7680.154 in the same stable update train. Apply the corresponding Chromium security updates from downstream vendors 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 activity2

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