As of , CVE-2025-48633 in Android Framework is on CISA's list of exploited vulnerabilities: CISA listed it on . Our patch-first group: Patch soon.
CVE-2025-48633
Android Framework: Information Disclosure. Exploited, and in our Patch soon group.
Our patch-first group
Patch soon
CISA's 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.
Patch infofixed versions and vendor advice
What to install
Affects Google Android 13, 14, 15 and 16.
The record's list of affected products names no fixed version.
Vendor advice
Vendor advice: source.android.com, from CISA's entry.
- EPSS score
- 0.00Higher than 17% of the CVEs EPSS scores.
EPSS estimates the chance of exploitation activity in the next 30 days.
- Exploited
- Yes CISA listed it on 2 December 2025
- US federal deadline
- 23 December 2025 21 days after CISA listed it. US federal civilian agencies must fix it by then.
- Used in ransomware campaigns
- Not known to CISA
- EPSS when listed
- No score that day The EPSS file of the day CISA listed it has no score for it.
- Public exploit
- None found Neither Metasploit nor Exploit-DB lists one.
Since listing
EPSS since listing
EPSS for CVE-2025-48633 since CISA listed it, on the days its value to 2 decimals changed. EPSS scores by FIRST.
Show the numbers
| From | EPSS |
|---|---|
| 0.01 | |
| 0.00 |
Timeline
What happened when
- CISA added it to its list of exploited vulnerabilities.
- The CVE record was published.
- The US federal deadline to fix it.
CISA's required action
What CISA says to do
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Read further: CISA's catalog
The flaw
What the flaw is
Android Framework contains an unspecified vulnerability that allows for information disclosure.
CISA's 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.
The CVE record's description, from google_android
- CVE published
- 8 December 2025
- Assigned by
- google_android
- CVSS
- 5.5 Medium (CVSS 3.1, from CISA-ADP)
- CISA SSVC, exploitation
- active
- CISA SSVC, automatable
- no
- CISA SSVC, technical impact
- partial
Same product
Framework: other exploited entries
| Vulnerability | Product | Our group | Listed | Deadline | EPSS |
|---|---|---|---|---|---|
| CVE-2023-35674Privilege Escalation | Framework | Patch soon | Due | 0.03 | |
| CVE-2025-48595Integer Overflow | Framework | Patch soon | Due | 0.02 | |
| CVE-2023-20963Privilege Escalation | Framework | Patch soon | Due | 0.01 | |
| CVE-2024-43093Privilege Escalation | Framework | Patch soon | Due | 0.01 | |
| CVE-2025-48572Privilege Escalation | Framework | Patch soon | Due | 0.00 |
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)