CVE-2025-48633mediumunder attack

CVE-2025-48633: medium-severity vulnerability in Google Android

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

43Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA.

ssvc Attendcvss 5.5epss 0.3%
from disclosure to weapon
Published on NVDDec 8
CISA KEVDec 2
Action required by CISAfederal deadline: 2025-12-23

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

In short

A flaw in Android's Device Policy Manager allows someone to add a Device Owner account after the device has already been set up, bypassing normal security checks. This could let an attacker gain administrative control over the device without needing special permissions or user approval.

Technical detail

CVE-2025-48633 exploits a logic error in hasAccountsOnAnyUser() of DevicePolicyManagerService.java that permits Device Owner provisioning post-setup. The attack vector is local; no additional privileges or user interaction required. Successful exploitation results in privilege escalation to Device Owner level, granting administrative device control.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

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/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected products
Google · Android