CVE-2025-48654: High severity Google Android vulnerability

Published Mar 2, 2026

Updated

In onStart of CompanionDeviceManagerService.java, there is a possible confused deputy 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.

Affected Software

4 affected components

Google Android=16.0

Google Android=16.0-qpr2_beta_1

Google Android=16.0-qpr2_beta_2

Google Android=16.0-qpr2_beta_3

Event History

Mar 2, 2026

CVE Published

via MITRE·06:42 PM

Data Sourced

via MITRE·06:42 PM

DescriptionWeakness

Data Sourced

via NVD·07:16 PM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2025-48654?

CVE-2025-48654 is classified as a high-severity vulnerability that allows local escalation of privilege due to a logic error.

How do I fix CVE-2025-48654?

To fix CVE-2025-48654, you should update affected Android devices to the latest security patches provided by Google.

What versions of Android are affected by CVE-2025-48654?

CVE-2025-48654 affects Google Android version 16.0 and its beta variations, including qpr2_beta_1, qpr2_beta_2, and qpr2_beta_3.

Is user interaction required to exploit CVE-2025-48654?

No, user interaction is not needed for exploiting CVE-2025-48654.

What is the nature of the vulnerability in CVE-2025-48654?

CVE-2025-48654 involves a confused deputy problem due to a logic error in the CompanionDeviceManagerService.java.