CVE-2025-48587: Google Android · Denial of Service
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium.
Data as of 30 Oct 2026, 11:52 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:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-48587, organizations and users should: 1) Monitor official Google Android security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 2) Restrict local access to devices by enforcing strong physical security controls and limiting installation of untrusted applications that could exploit local vulnerabilities. 3) Employ mobile device management (MDM) solutions to monitor device health and detect abnormal service crashes or instability indicative of exploitation attempts. 4) Consider disabling or restricting the ProfilingService if feasible and if it does not impact critical functionality, as a temporary workaround until patches are released. 5) Conduct regular security audits and vulnerability assessments on Android devices to identify and remediate local privilege escalation or DoS risks. 6) Educate users on the risks of installing untrusted apps or granting unnecessary permissions that could facilitate local attacks. These steps go beyond generic advice by focusing on controlling local access, monitoring service health, and applying targeted workarounds.
Description
In multiple functions of ProfilingService.java, there is a possible persistent denial of service due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.