CVE-2026-12015 is a high-severity use-after-free vulnerability in the Autofill component of Google Chrome affecting versions prior to 149.0.7827.115. The flaw can be triggered via a crafted HTML page and occurs after memory associated with an Autofill object is freed and subsequently reused, creating a condition where stale references may access invalid memory. According to the available vendor description, exploitation requires that the attacker has already compromised the renderer process. Under those conditions, the vulnerability can be used to read potentially sensitive information from browser process memory.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity use-after-free vulnerability in Chrome Autofill.
A high-severity use-after-free vulnerability in Chrome Autofill.
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.