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 WebCodecs

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

CVE-2026-3544 is a high-severity heap buffer overflow in the WebCodecs component of Google Chrome prior to version 145.0.7632.159. According to the provided content, a remote attacker could trigger an out-of-bounds memory write by convincing a target to load a crafted HTML page. The issue affects Chromium/Chrome builds before the fixed 145.0.7632.159 release and is described by Google as a heap buffer overflow in WebCodecs.

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 arbitrary code execution in the context of the Chrome renderer or otherwise cause process compromise through memory corruption. The provided Chromium package context also notes that the broader set of Chromium issues could result in arbitrary code execution, denial of service, or information disclosure. At minimum, this vulnerability enables an out-of-bounds heap write and could plausibly be used for browser crash or further exploitation.

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 use of untrusted websites and untrusted HTML content, and by enforcing rapid browser update policies across enterprise fleets. No specific workaround short of updating is provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to version 145.0.7632.159 or later. For Windows and macOS, Google moved the Stable channel to 145.0.7632.159/160; for Linux, to 145.0.7632.159. Enterprise administrators should deploy the patched version across managed endpoints using standard update policy mechanisms.
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

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

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 activity7

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