Loading vulnerability…
CVE-2026-106313 is an incorrect-authorization vulnerability in the Browser component of Google Chrome for Android before version 155.0.8059.39. A local attacker leveraging social engineering can obtain sensitive information through a co-installed application.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect authorization vulnerability in Google Chrome for Android before version 155.0.8059.39 permits a local attacker using social engineering and a co-installed application to obtain sensitive information. The reference assigns a medium Chromium severity and a CVSS v3 base score of 5.1. Nessus flags the Debian Chromium package based on vendor-reported package presence, rather than verified exploitation, and reports no vendor-supplied patch for the flagged package.
An incorrect authorization vulnerability in Google Chrome on Android before version 155.0.8059.39 allows a local attacker using social engineering and a co-installed app to obtain sensitive information. Chromium rates its security severity as Medium.
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.