CVE-2025-48633 — Android Framework Information Disclosure Vulnerability

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

01What is this vulnerability?

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.

02Affected products

Vendor	Product	Versions
Google	Android	16, 15, 14, 13

03Active exploitation status

Yes — actively exploited. Added to the CISA KEV catalog on 2025-12-02. Ransomware use: Unknown.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Open the Sigma generator with a pre-filled prompt for this CVE to draft a starting detection in your stack of choice:

Open in Sigma generator →

07Related CVEs

No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.

08Timeline

• Published: 2025-12-08T16:57:49.260Z
• Last modified: 2026-02-26T16:57:12.360Z
• Added to CISA KEV: 2025-12-02
• BOD 22-01 due: 2025-12-23

09References

• android.googlesource.com — https://android.googlesource.com/platform/frameworks/base/+/d00bcda9f42dcf272d32…
• source.android.com — https://source.android.com/security/bulletin/2025-12-01