CVSS 3.1
5.9 mediumCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:HCVE-2026-59020
Medium (5.9) in google android. EPSS 0.06% estimated probability of exploitation activity in the next 30 days.
On this page
In removeUserData of DevicePolicyManagerService.java, there is a possible denial of service due to a race condition. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation.
Severity
- EPSS
- 0.06% estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-59020 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59020?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59020?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59020 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:android | 14.0 |
| google:android | 15.0 |
| google:android | 16.0 |
| google:android | 16.0:qpr2 |
| google:android | 17.0 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.