dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Dec 2025.
AndroidOperating system · Google

CVE-2025-48633

MEDIUM · 5.5 CVSS v3.1 Published 2025-12-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A logic error in the hasAccountsOnAnyUser method of Android's DevicePolicyManagerService allows an attacker to add a Device Owner after the device provisioning process has completed. This bypasses the intended restriction that Device Owner assignment should only occur during initial setup, enabling local privilege escalation without user interaction.

MitigationApply the vendor-supplied Android security patch containing the fix for CVE-2025-48633. Organizations using MDM solutions should verify their Android fleet is receiving the latest security updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 13.0= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Run 'getprop ro.build.version.release' or go to Settings > About Phone to verify the Android version
    Affected if The version is 13.0, 14.0, 15.0, or 16.0 exactly (not a later patch version)
  2. Identify any configured Device Owner
    Run 'dumpsys device_policy' and look for entries under 'Device Owner:' or 'Device Owners:' sections. Also check 'dumpsys device_policy | grep -i owner'
    Affected if Any Device Owner is present on the device (this feature is typically only intended for MDM/enterprise enrollment during initial setup)
  3. Check device provisioning state
    Run 'dumpsys device_policy' and look for 'User Setup Complete' status or provisioning related flags in the output
    Affected if The device shows as fully provisioned (setup complete) but has a Device Owner assigned, indicating potential post-provisioning assignment
  4. Review device admin and policy receivers
    Run 'dumpsys package' and filter for DeviceAdminReceiver implementations, or check 'dpm list-owners' if available in your build tools
    Affected if There are Device Adminreceivers that were not intentionally installed during enterprise/MDM enrollment

A device is affected if it runs Android 13.0-16.0 and has a Device Owner assigned after the initial device setup was completed, as evidenced by the provisioning state showing complete while a Device Owner exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch android.googlesource.com →
Interim mitigation

Apply the vendor-supplied Android security patch containing the fix for CVE-2025-48633. Organizations using MDM solutions should verify their Android fleet is receiving the latest security updates.

Recommended fix Moderate confidence

Android Security Patch Level that includes the fix for CVE-2025-48633 (refer to Android Security Bulletin)

  1. Check the Android Security Bulletin for the month containing the fix for CVE-2025-48633
  2. Apply the appropriate Android security patch level (SPL) that includes the fix for this vulnerability
  3. Verify the DevicePolicyManagerService.java hasAccountsOnAnyUser method no longer allows Device Owner addition post-provisioning

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48633 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data