# CVE-2025-48633: Android Framework Information Disclosure

> A logic error in Android's DevicePolicyManagerService allows local attackers to escalate privileges by adding a Device Owner without user interaction.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 2 Dec 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2025
- **Updated:** 26 Feb 2026
- **Also known as:** A-417988098, ASB-A-417988098, GHSA-2jv4-596w-g9hj

## What is CVE-2025-48633?

CVE-2025-48633 is a medium-severity vulnerability in Google Android, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-48633?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2025-48633?

Apply the vendor's patch. US federal agencies must fix it by 23 Dec 2025.

## Is CVE-2025-48633 being exploited?

Yes. Attackers have exploited CVE-2025-48633 in the wild since at least 2 Dec 2025.

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48633 and fix it if it is affected.

What it is: CVE-2025-48633 is a medium-severity vulnerability in Google Android, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-48633 in the wild since at least 2 Dec 2025.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48633/ (Markdown: https://insights.sbomify.com/CVE-2025-48633/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48633
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48633
- OSV: https://osv.dev/vulnerability/CVE-2025-48633

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48633/
Summaries are generated and may contain mistakes; the official description above is the record.