CVE-2026-12007 is a critical use-after-free vulnerability in the Core component of Google Chrome on Windows prior to version 149.0.7827.115. The flaw can be triggered by a remote attacker through a crafted HTML page, causing Chrome to access memory after it has been freed. As a memory-safety error in a browser core component, successful exploitation can corrupt process memory and enable arbitrary code execution in the context of the browser 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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in Google Chrome Core that can enable remote code execution via a crafted HTML page.
A critical use-after-free vulnerability in a Chrome core component that can lead to memory corruption and potentially arbitrary code execution via a specially crafted web page.
A critical use-after-free vulnerability in the Chrome Core component that could potentially allow attackers to execute arbitrary code or gain control over affected systems.
A critical use-after-free vulnerability in Chrome Core.
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.