CVE-2025-0092: Google Android · Information disclosure
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Android | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Ensure all Android devices are updated promptly once Google or device manufacturers release patches addressing CVE-2025-0092. 2) Educate users about the risks of accepting unexpected Bluetooth pairing requests or interacting with suspicious UI prompts related to Bluetooth bonding. 3) Implement mobile device management (MDM) policies to restrict or monitor Bluetooth usage, especially in sensitive environments, including disabling Bluetooth when not needed or enforcing strict pairing policies. 4) Use endpoint security solutions capable of detecting anomalous Bluetooth activity or unauthorized attempts to access Bluetooth services. 5) For critical environments, consider restricting physical access to devices to prevent proximal attackers from exploiting Bluetooth vulnerabilities. 6) Monitor security advisories from Google and Android OEMs for updates and apply them as soon as available. 7) Conduct regular security awareness training emphasizing the importance of cautious user interaction with device prompts that could lead to information disclosure.
Description
In handleBondStateChanged of AdapterService.java, there is a possible permission bypass due to misleading or insufficient UI. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.