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

Heap buffer overflow in ANGLE in Google Chrome

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

CVE-2026-4448 is a high-severity heap buffer overflow in ANGLE affecting Google Chrome prior to version 146.0.7680.153. The available information indicates that a remote attacker could trigger heap corruption by convincing a user to visit a crafted HTML page. ANGLE, Chrome’s graphics abstraction layer used in rendering-related paths, is the affected component. No vulnerable function or code path has been publicly disclosed in the provided content, but the issue is characterized as a heap-based memory corruption flaw reachable through web content.

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 result in heap corruption in the browser process and may enable arbitrary code execution in the context of the targeted Chrome process. Based on the vendor summary for this release, Chrome memory corruption vulnerabilities of this class may also lead to denial of service via browser crash, and potentially information disclosure depending on exploitability and surrounding conditions.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and web content, restricting browser use in high-risk environments, and enforcing browser sandboxing and least-privilege controls at the OS and enterprise policy level. Network- or content-filtering controls that reduce access to malicious or unknown sites may lower risk, but no mitigation in the provided content eliminates the vulnerability short of updating to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later. The referenced Chrome Stable channel update includes fixes for this vulnerability; patched versions listed in the provided content are 146.0.7680.153 and 146.0.7680.154 for Windows and macOS, and 146.0.7680.153 for Linux. Apply the latest available vendor update rather than remaining on the minimum fixed build.
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.