Loading vulnerability…
CVE-2026-106249 is an incorrect-authorization vulnerability in the Autofill feature of Google Chrome on Android before version 155.0.8059.39. A remote attacker can use a crafted HTML page to obtain sensitive information. The specific authorization check and the types of information exposed 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.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect authorization vulnerability in Google Chrome's Autofill functionality on Android permits sensitive information disclosure through a crafted HTML page. The Nessus plugin also identifies affected Debian Chromium packages as vendor-unpatched. Chromium rates the flaw Low, whereas the plugin reports High severity and a CVSS v3 base score of 8.8.
An incorrect authorization vulnerability in Google Chrome's Autofill feature on Android, affecting versions before 155.0.8059.39. A remote attacker could obtain sensitive information through a crafted HTML page. Chromium rates the vulnerability as Low severity.
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.