Skip to content
Server Security Center
KEVmedium5.5

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

CVE-2025-48633 explained

CVE-2025-48633 is a logic error in hasAccountsOnAnyUser of DevicePolicyManagerService.java in the Android Framework. It could allow a Device Owner to be added after provisioning, leading to local escalation of privilege. CISA lists it as known exploited, so affected Android devices should be patched promptly.

Impact

A local attacker with low privileges could add a Device Owner after the device has been provisioned. No additional execution privileges and no user interaction are needed. The CVSS rating shows high confidentiality impact with no integrity or availability impact. CISA rates it as not automatable, with partial technical impact. CISA's Known Exploited Vulnerabilities catalog confirms attackers use it. Ransomware use is unknown.

Who is affected

The CVE record lists Google Android versions 13, 14, 15 and 16 as affected. It names no fixed version. That does not mean no fix exists. Check the vendor advisory for the security patch level that addresses this issue.

Written with AI from the data on this page and checked against it automatically.

Official 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.

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 Android
    Affected
    • 13
    • 14
    • 15
    • 16
    Fixed in
    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.

What to do

  1. Check the Android vendor advisory for the security patch level that fixes CVE-2025-48633.
  2. Install that security update on all managed devices running Android 13, 14, 15 or 16.
  3. Use your device management tooling to find devices that have not received the update.
  4. Review managed devices for unexpected Device Owner or device administration changes.
  5. If mitigations are unavailable for a device, follow CISA's guidance and discontinue its use.

The CVE record names no fixed version. Follow the vendor advisory to find the security update that addresses this issue. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Prioritize devices that cannot receive updates.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Questions about CVE-2025-48633

Is CVE-2025-48633 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-12-02, which means attackers are known to use it. Whether it is used in ransomware campaigns is unknown.
Can it be exploited remotely?
The CVSS vector rates the attack as local, requiring low privileges and no user interaction. CISA rates it as not automatable.
What is the deadline for US federal agencies?
Under CISA's catalog, US federal agencies must act by 2025-12-23. They must apply vendor mitigations or discontinue use if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

References

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.