Loading vulnerability…
CVE-2026-79012 is a critical use-after-free vulnerability in the Safe Browsing component of Google Chrome for macOS before version 152.0.7977.65. A remote attacker can use a crafted HTML page and social engineering to trigger the memory-safety flaw, resulting in arbitrary code execution outside Chrome's sandbox.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical use-after-free vulnerability in Chrome's Safe Browsing component.
Critical use-after-free vulnerability in Google Chrome addressed by Chrome 152.
A remotely reachable vulnerability requiring user interaction, with high confidentiality, integrity, and availability impact according to the supplied CVSS v3 vector. The content identifies Debian Linux 11.0–14.0 and Debian's Chromium package as affected targets.
A critical use-after-free vulnerability in Google Chrome Safe Browsing on macOS before version 152.0.7977.65. A remote attacker could use a crafted HTML page and social engineering to execute arbitrary code outside Chrome's sandbox.
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.