CVE-2025-48633: Android Framework Information Disclosure
Android Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2025-12-02.
- CVSS v3.1 (CISA ADP)
- 5.5
- medium
- EPSS (exploit probability, 30 days)
- 0.3%
- higher than 17.2% of all CVEs
- Added to CISA KEV
- 2025-12-02
- US federal due date 2025-12-23
- Automatable (CISA SSVC)
- no
- technical impact: partial
What is CVE-2025-48633?
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.
CISA 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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google AndroidAffectedFixed in
- 13
- 14
- 15
- 16
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Google Android |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: source.android.com/security/bulletin/2025-12-01
- CISA's deadline for US federal agencies: 2025-12-23 (passed) – a useful benchmark for everyone else, too.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Partial – limited control or information
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.