CVE-2026-12022 is a high-severity race condition in the Safe Browsing component of Google Chrome on macOS affecting versions prior to 149.0.7827.115. The flaw can be triggered through a malicious file and is exploitable by a remote attacker who has already compromised the renderer process. Under those conditions, the race may allow the attacker to break out of Chrome's sandbox on Mac. The issue is classified as a race condition and affects the browser's security boundary enforcement rather than being described as a direct memory corruption bug in the available information.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A race condition vulnerability in Safe Browsing in Google Chrome on Mac that could allow a remote attacker with a compromised renderer process to potentially escape the sandbox via a malicious file.
A high-severity race condition vulnerability in Chrome Safe Browsing.
A high-severity race condition vulnerability in Chrome Safe Browsing.
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.