CVE-2025-48601: Google Android · Elevation of Privilege
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 10:12 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Dec 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
To mitigate CVE-2025-48601, European organizations should implement the following specific measures: 1) Enforce strict local device access controls, including strong authentication and device encryption, to prevent unauthorized local access. 2) Monitor device logs and behavior for signs of abnormal crashes or privilege escalations that could indicate exploitation attempts. 3) Restrict installation of untrusted or unnecessary applications that could be used as vectors to gain local access. 4) Educate users about physical device security to reduce risks of local exploitation. 5) Deploy mobile device management (MDM) solutions to enforce security policies and remotely manage affected devices. 6) Prepare for prompt deployment of official patches from Google once released, including testing and staged rollouts to minimize operational disruption. 7) Consider network segmentation and limiting sensitive data access from mobile devices until patches are applied. 8) Conduct regular security assessments and penetration tests focusing on mobile device security to identify potential exploitation paths. These measures go beyond generic advice by focusing on local access prevention, monitoring, and proactive patch management tailored to the nature of this vulnerability.
Description
In multiple locations, there is a possible permanent denial of service due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.