CVE-2025-48633
MediumExploitedPublic exploitIn hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code.
Published Dec 8, 2025 · Updated Oct 14, 2026 · Also known as A-417988098, ASB-A-417988098
Key Facts
Patch immediately- CVE-2025-48633 is a medium-severity vulnerability (CVSS 5.5 v3.1) affecting Android (Google), platform/frameworks/base (android).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Dec 1, 2025. Public exploit code is available.
- EPSS estimates a 0.3% probability of exploitation in the next 30 days.
- Fixed versions are available, including platform/frameworks/base 13:2025-12-01, platform/frameworks/base 14:2025-12-01, platform/frameworks/base 15:2025-12-01.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
0.3%
Higher than 16.8% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2025-48633 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Dec 2, 2025 | Dec 23, 2025 | Not reported |
| Industry KEV feed | Dec 1, 2025 | Dec 23, 2025 | Not reported |
| CIRCL KEV | Dec 2, 2025 | Dec 23, 2025 | Not reported |
| ENISA EUVD | Dec 2, 2025 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected Products
6 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| AndroidGoogle | 13.0, 14.0, 15.0, 16.0, >= 16 | n/a |
| platform/frameworks/baseandroid | >= 16-qpr2-next:0 | 16-qpr2-next:2025-12-01 |
Patched Releases
platform/frameworks/base
13:2025-12-01, 14:2025-12-01, 15:2025-12-01, 16-qpr2-next:2025-12-01, 16:2025-12-01
Timeline
Added to Industry KEV feed
Dec 1, 2025
Added to CISA KEV
Dec 2, 2025
Added to CIRCL KEV
Dec 2, 2025
Added to ENISA EUVD
Dec 2, 2025
Publicly disclosed
Dec 8, 2025
Last updated
Oct 14, 2026
References
- advisoryhttps://source.android.com/security/bulletin/2025-12-01
- patchhttps://android.googlesource.com/platform/frameworks/base/+/d00bcda9f42dcf272d329e9bf9298f32af732f93
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
FAQ
Common Questions.
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.
Affected: Android (Google) versions 13.0, 14.0, 15.0, 16.0, >= 16; platform/frameworks/base (android) versions >= 16-qpr2-next:0. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Dec 1, 2025.
Yes. It was added on Dec 2, 2025 with a federal remediation due date of Dec 23, 2025.
Public exploit code is available.
Fixed versions are available, including platform/frameworks/base 13:2025-12-01, platform/frameworks/base 14:2025-12-01, platform/frameworks/base 15:2025-12-01.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2025-48633 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo