CVE-2025-48633KEV · OVERDUE

Android Framework Information Disclosure Vulnerability

Medium · published December 8, 2025

Patch now

The score understates this — it's already being exploited

CVSS calls it medium at 5.5. It is confirmed in active exploitation. It sits in the 17.0th percentile for exploit probability.

304
days past CISA
deadline
CVSS v3.1
5.5
EPSS
0%
Percentile
17.0
In the wild
Confirmed
What it is

⚠️ A sneaky logic error in DevicePolicyManagerService.java could let an attacker add a Device Owner without breaking a sweat! 😱 Think of it like a hotel check-in process where the front desk accidentally gives out keys to rooms without verifying the guests — suddenly, anyone can walk into any suite they please! This vulnerability could allow an attacker to escalate their privileges locally, gaining unauthorized control over the device. They could potentially change settings, install malicious applications, or even access sensitive user data, all without any user interaction required. That's a recipe for trouble!

Put simply

Think of it like a hotel check-in process where the front desk accidentally gives out keys to rooms without verifying the guests — suddenly, anyone can walk into any suite they please! In the hasAccountsOnAnyUser method, a logic flaw allows an attacker to add their account as a Device Owner post-provisioning, bypassing intended security checks. This means they can gain elevated permissions on the device without needing any elevated execution privileges.

What to do

This vulnerability could allow an attacker to escalate their privileges locally, gaining unauthorized control over the device. They could potentially change settings, install malicious applications, or even access sensitive user data, all without any user interaction required. That's a recipe for trouble! To mitigate this risk, ensure you're running the latest device firmware and apply any available patches immediately. Audit your Device Policy Manager configurations and consider implementing stricter checks during the account provisioning process. You've got this! Stay proactive, and with these steps, you’ll keep your devices secure! 🛡️

The record
Technical detail
CVSS v3.1
5.5 · MEDIUM
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS v4.0
Not supplied
EPSS
0.00262 · 17.0th percentile
Published
2025-12-08T22:16Z
KEV added
2025-12-02 · due 2025-12-23
Affected products (4)
ProductVersionsFixed in
google/androidall versions—
google/androidall versions—
google/androidall versions—
google/androidall versions—
References (3)
EPSS history
Timeline
  • 08 DEC 16:57Z
    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
    cvelistv5
  • 02 DEC 00:00Z
    Added to CISA KEV — remediate by Dec 23
    kev