CVE-2025-48585: 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, 06:59 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-48585, organizations should first monitor official Google security advisories for patches addressing this vulnerability and apply them promptly once available. Until patches are released, limiting local access to Android 16 devices is critical; this includes enforcing strong device access controls, disabling unnecessary local interfaces, and restricting installation of untrusted applications that could exploit the vulnerability. Employing mobile device management (MDM) solutions to enforce security policies and monitor device behavior can help detect anomalous activity related to ProfilingService disruptions. Additionally, educating users about the risks of installing unverified apps and maintaining updated security configurations reduces the likelihood of local exploitation. For high-security environments, consider isolating critical Android devices or using alternative versions not affected by this vulnerability. Finally, implementing robust incident response procedures to quickly recover from denial of service conditions, such as restarting affected services or devices, will minimize operational impact.
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.