Loading vulnerability…
CVE-2026-4445 is a high-severity use-after-free vulnerability in the WebRTC component of Google Chrome. The flaw affects Chrome versions prior to 146.0.7680.153 and can be triggered by a remote attacker via a crafted HTML page. The vulnerability is caused by incorrect lifetime management of memory in WebRTC, leading to a dangling pointer condition after an object has been freed. Subsequent access to the freed memory can result in heap corruption. In a browser exploitation context, this class of bug can be used to destabilize the renderer or, with successful exploitation, to achieve arbitrary code execution within the target process.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior Chrome WebRTC use-after-free vulnerability referenced for historical comparison.
A high-severity use-after-free vulnerability in Chrome's WebRTC component.
One of multiple Palo Alto Networks product vulnerabilities listed in the advisory; no specific technical detail provided in the content excerpt.
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.