CVE-2025-48633
Exploited in the wild. In CISA KEV since 2025‑12‑02. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
- Google AndroidAffected: 16Upgrade to: not statedAffected: 15Upgrade to: not statedAffected: 14Upgrade to: not statedAffected: 13Upgrade to: not statedStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Coverage timeline
0 publishersAdded to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2025-12-02.
US federal agencies must remediate by 2025-12-23.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 17th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Rising.
Lifecycle
9 events over 309 days, from the signal feeds we watch.
- Patch availablerecord updated
- Patch availablerecord updated
- Patch availablerecord updated
- Publishedweakness classified
- Added to CISA KEV
Affected products
And 2 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Scored 5.5 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Android, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI