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 WebAudio

IdentifiersCVE-2026-4677CWE-125· Out-of-bounds Read

CVE-2026-4677 is a high-severity out-of-bounds read vulnerability in the WebAudio component of Google Chrome. The issue is described by Google as an inappropriate implementation in WebAudio affecting Chrome versions prior to 146.0.7680.165. A remote attacker can trigger the flaw by causing a target to load a crafted HTML page, which leads Chrome to read memory outside the intended bounds during WebAudio processing. Publicly available source material does not provide the specific vulnerable function or code path, and Google restricted detailed bug information pending broad patch adoption.

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 induce an out-of-bounds memory read in the browser process. Based on the available information, this can result in information disclosure and browser instability or denial of service. The supplied context also notes that high-severity Chrome memory-safety flaws may contribute to broader compromise chains, but no specific public evidence in the provided material confirms standalone remote code execution for CVE-2026-4677 itself.

Mitigation

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

Apply the vendor update as the primary mitigation. Until patching is complete, reduce exposure by limiting access to untrusted or attacker-controlled websites and HTML content, and by enforcing rapid browser restart after update deployment so the fix becomes active. No vulnerability-specific workaround is provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to a fixed version. The provided content states that Chrome versions prior to 146.0.7680.165 are vulnerable, and Google released fixes in Chrome 146.0.7680.164/165 for Windows and Mac and 146.0.7680.164 for Linux as part of the Stable channel rollout. Ensure the browser is fully restarted after updating, as the protections do not take effect until relaunch. Enterprise administrators should deploy the patched Chrome builds through normal patch-management processes.
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.