BaseFortify

Publication date: 2025-12-08

Last updated on: 2025-12-09

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-08

Last Modified

2025-12-09

Generated

2026-07-06

AI Q&A

2025-12-10

EPSS Evaluated

2026-07-05

NVD

CVE-2025-48633

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	13.0
google	android	14.0
google	android	15.0
google	android	16.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-NVD-CWE-noinfo

Attack-Flow Graph

Mitigation Strategies

Apply the security patch that includes the fix committed on September 16, 2025, which addresses the vulnerability in DevicePolicyManagerService. Ensure your Android device is updated to the latest security patch level that contains this fix, as described in the Android framework base repository update. Keeping your device updated with the latest security patches is the recommended immediate mitigation step. [2]

Executive Summary

This vulnerability is a logic error in the hasAccountsOnAnyUser function of DevicePolicyManagerService.java that allows an attacker to add a Device Owner after device provisioning. This can be exploited locally without needing any additional execution privileges or user interaction.

Impact Analysis

The vulnerability can lead to local escalation of privilege, meaning an attacker with local access could gain higher privileges on the device than intended, potentially compromising device security and control.

Hi! I’m here to help you understand CVE-2025-48633. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70