CVE-2025-48633: Android Framework Information Disclosure Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by google_android, published 2025-12-08).

How it can be exploited

Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: partial.

On CISA KEV since
2025-12-02
US federal deadline
2025-12-23
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-15136, CNNVD-202512-903, EUVD-2025-201737, GHSA-2jv4-596w-g9hj

Exploit Observer links 1 piece of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (1)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (1)

Vulnerability databases and vendor advisories (5)

Catalogue entries, not exploit evidence.

News (1)

14 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.003
low predicted chance of attack
VEDAS
0.514
some exploit evidence
On CISA KEV
Yes, since 2025-12-02
Detection rule
Out of scope (local)
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2025-48633 EPSS over time2025-122026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2025-48633 VEDAS over time2025-122026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Google Androidversion 16
version 15
version 14
version 13
Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: google android, google_inc android.

How to fix it

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.

Vendor guidance:

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.