Loading vulnerability…
CVE-2026-12015 is a use-after-free vulnerability in the Autofill component of Google Chrome before version 149.0.7827.115. A remote attacker who has already compromised the renderer process can use a crafted HTML page to obtain potentially sensitive information from process memory. The vulnerability also affects Chromium-based Microsoft Edge before the release incorporating the Chromium fix.
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 use-after-free vulnerability in Google Chrome Autofill enables disclosure of potentially sensitive process memory through a crafted HTML page, provided the attacker has already compromised the renderer process. The reference lists Chromium severity as High and a CVSS v3 base score of 5.3. It recommends updating the Echo chromium package to 149.0.7827.114 or later, while describing affected Google Chrome versions as earlier than 149.0.7827.115.
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.