Live › vulnerability › CVE-2025-48633
Go to dashboardAn unspecified flaw in the Android Framework lets an attacker read information they should not see. CISA lists it as exploited in the wild, so attacks are happening.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Android Framework | vendor | – | – |
| google android | vendor | = 13.0 | – |
| google android | vendor | = 14.0 | – |
| google android | vendor | = 15.0 | – |
| google android | vendor | = 16.0 | – |
Unknown from the sources.
Apply the Android security patch that addresses CVE-2025-48633 per vendor instructions; the sources do not name the patch level.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2025-48633")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.