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

Heap buffer overflow in CSS in Google Chrome

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

CVE-2026-4442 is a high-severity heap buffer overflow in the CSS component of Google Chrome affecting versions prior to 146.0.7680.153. According to the provided content, a remote attacker could trigger heap corruption by causing a victim to load a crafted HTML page. The issue is described as a heap buffer overflow in CSS processing, indicating that malformed or attacker-controlled web content can cause an out-of-bounds write or related memory corruption condition in heap-allocated memory during CSS handling. Google/Chromium classified the issue as High severity.

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. As indicated by the supporting content for this Chrome release, memory corruption vulnerabilities in Chrome may enable arbitrary code execution, denial of service via browser crash, or potentially information disclosure, depending on exploitability and runtime conditions. For this specific flaw, the confirmed impact from the provided data is remote triggering of heap corruption through crafted web content.

Mitigation

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

Until patching is completed, reduce exposure by limiting access to untrusted websites and preventing users from opening attacker-controlled HTML content. Enterprise defenders can use browser update enforcement, restrict unsupported/outdated Chrome or Chromium builds, and apply standard browser hardening controls such as site isolation and least-privilege execution where available. However, mitigation is only partial; vendor patching is the primary corrective action.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome/Chromium to a fixed version. The provided content states that Chrome versions prior to 146.0.7680.153 are affected; patched releases include 146.0.7680.153 and 146.0.7680.154 for Windows and macOS, and 146.0.7680.153 for Linux. Apply the vendor-provided update through normal browser or OS package update channels.
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 activity4

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