In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion.
- Exploited
- No known exploitation
- Fix
- Fixed in 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 16-qpr2, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 16-qpr2, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
What to do
Upgrade to a fixed version: 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-59008
What does this mean?
The bug is in the setApplicationRestrictions function of DevicePolicyManagerService.java in Android. Its advisory classifies it as a denial-of-service issue caused by resource exhaustion, meaning the affected component can be driven to use up resources and stop working properly.Source: source.android.com
Am I affected, and how do I check?
The checked facts name Google Android but list no affected version ranges or specific setups. To check a device's version, look under Settings, About phone. The fixed releases listed are 16-qpr2 and 17.Source: source.android.com
What should I do about it?
Install a security update that includes the fix, which the advisory lists as Android 16-qpr2 or Android 17.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data