Loading vulnerability…
CVE-2026-106342 is an information-disclosure vulnerability in the Autofill component of Google Chrome versions earlier than 155.0.8059.39. A remote attacker can use a crafted HTML page to obtain sensitive information. The specific vulnerable function, disclosure mechanism, and types of exposed information are not identified.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-disclosure vulnerability in Google Chrome Autofill before version 155.0.8059.39 allows a remote attacker to obtain sensitive information through a crafted HTML page. The Nessus advisory identifies affected Chromium packages without an available vendor patch and states there is no known solution. It rates the vulnerability High with a CVSS v3 base score of 8.8, while the description gives Chromium's severity as Medium.
A medium-severity information disclosure vulnerability in Google Chrome Autofill affecting versions before 155.0.8059.39. A remote attacker could obtain sensitive information through a crafted HTML page.
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.