Use-after-free in Google Chrome Base
CVE-2026-4441 is a critical use-after-free vulnerability in the Base component of Google Chrome prior to version 146.0.7680.153. The flaw is described as a memory lifetime management error in which previously freed memory can be accessed again, creating a condition for heap corruption. According to the provided content, a remote attacker could trigger the issue by convincing a user to load a crafted HTML page. In Chrome’s multi-component architecture, such memory corruption flaws are commonly exploitable for renderer compromise and potentially further code execution depending on exploit reliability and available sandbox escape chains, but the provided content specifically confirms heap corruption potential and broader arbitrary code execution risk across the affected update set.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.