CVE-2025-48626: Google Android · Elevation of Privilege
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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-48626, organizations should: 1) Monitor official Google security advisories and apply patches immediately once available. 2) Restrict background application launches through device management policies to limit unauthorized app execution. 3) Employ mobile threat defense solutions that detect anomalous app behavior indicative of privilege escalation attempts. 4) Enforce the principle of least privilege by limiting app permissions and user privileges on devices. 5) Use application whitelisting and sandboxing to reduce the attack surface. 6) Conduct regular security audits and vulnerability assessments on mobile device fleets. 7) Educate users about the risks of installing untrusted applications and encourage the use of official app stores. 8) Implement network-level controls to detect and block suspicious traffic originating from compromised devices. These steps provide layered defense until official patches are deployed.
Description
In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
References
- android.googlesource.com/platform/packages/apps/Launcher3/+/7628af9bf77f1d145359bf4075a6674574cae496 (opens in a new tab)
- android.googlesource.com/platform/frameworks/base/+/9fb37191609f7cb7b2374531cafb2d00ec8b4bec (opens in a new tab)
- source.android.com/security/bulletin/2025-12-01 (opens in a new tab)