CVE-2025-48633
Android Framework Information Disclosure Vulnerability
Android Framework
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 2 December 2025. US federal agencies were required to remediate it by 23 December 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.3%, which is higher than 17.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2025-48633 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-48633.
What does CVE-2025-48633 affect?
CVE-2025-48633 affects Android Framework. 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.
How severe is CVE-2025-48633?
CVE-2025-48633 is rated MEDIUM with a CVSS base score of 5.5. EPSS puts the probability of exploitation in the next 30 days at 0.3%, higher than 17.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 December 2025.
How should organisations respond to CVE-2025-48633?
Apply the vendor patch for Android Framework as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.