CVE-2026-0015: 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 1% 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-2026-0015, organizations and users should monitor for official patches or security updates from Google and apply them promptly once available. Until patches are released, limiting local access to trusted users and applications can reduce exploitation risk. Employing mobile device management (MDM) solutions to enforce strict app installation policies and restrict untrusted local applications can help prevent exploitation. Regularly auditing installed apps and removing unnecessary or suspicious software reduces the attack surface. Additionally, educating users about the risks of installing untrusted apps and maintaining device physical security can further mitigate local exploitation. Developers should review and harden input validation in custom Android services and apps to avoid similar issues. Monitoring device logs for abnormal AppOpsService behavior may help detect exploitation attempts.
Description
In multiple locations of AppOpsService.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.