CVE-2025-26453: Google Android · Information Disclosure
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Android | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Enforce strict device access controls to limit local access to authorized users only, reducing the risk of local exploitation. 2) Restrict installation of untrusted or unnecessary applications that could leverage this vulnerability to access other users' data. 3) Monitor and audit multi-user Android devices for unusual access patterns or data exfiltration attempts. 4) Apply security policies that disable or limit multi-user profiles on corporate devices unless absolutely necessary. 5) Stay informed about official patches or updates from Google and prioritize timely deployment once available. 6) Use Mobile Device Management (MDM) solutions to enforce security configurations and restrict Bluetooth file transfer features if not required. 7) Educate users about the risks of sharing devices and the importance of maintaining separate user profiles with appropriate permissions. These targeted measures go beyond generic advice by focusing on controlling local access, application permissions, and device configuration to mitigate the specific cross-user data leak risk.
Description
In isContentUriForOtherUser of BluetoothOppSendFileInfo.java, there is a possible cross user data leak due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.