CVE-2025-48642: Google Android · Information Disclosure
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% 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 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-48642, organizations and users should: 1) Monitor official Google Android security advisories for patches addressing this vulnerability and apply updates promptly once available. 2) Restrict local access to Android devices by enforcing strong physical security controls and device access policies, including screen locks and user authentication. 3) Limit the number of users with local access privileges on shared or enterprise devices to reduce the attack surface. 4) Employ mobile device management (MDM) solutions to enforce security policies and monitor device integrity. 5) Educate users about the risks of local access vulnerabilities and encourage reporting of suspicious device behavior. 6) Consider deploying endpoint detection and response (EDR) tools capable of detecting anomalous local activities that may indicate exploitation attempts. 7) For highly sensitive environments, evaluate the use of hardware-backed security features and secure boot mechanisms to further protect against unauthorized local access. These steps go beyond generic advice by focusing on controlling local access vectors and preparing for timely patch deployment.
Description
In jump_to_payload of payload.rs, there is a possible information disclosure 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.