CVE-2025-48633
Android Framework Information Disclosure
- Published8 Dec 2025
- Added to CISA KEV2 Dec 2025
- Remediation due23 Dec 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
Frequently asked
Is CVE-2025-48633 being actively exploited?
Yes. CVE-2025-48633 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 2 Dec 2025.
How severe is CVE-2025-48633?
CVE-2025-48633 has a CVSS 3.1 base score of 5.5, rated medium. EPSS estimates a 0.26% probability of exploitation.
Which products are affected by CVE-2025-48633?
Affected products include Google Android.
How do I fix CVE-2025-48633?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-48633 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.