Security Digest · Vulnerability record · Known exploited

CVE-2025-48633: Android Framework Information Disclosure Vulnerability

Exploited in the wild (CISA KEV). 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.

CISA KEV · added 2025-12-02 CVSS 5.5 Medium EPSS 0.3% · p17

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Yes, if you run Android Framework. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2025-12-02, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2025-12-23; treat that as the outer limit, not the target.
  • EPSS 0.3%, percentile 17: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 17% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.

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.

CISA’s summary

Android Framework contains an unspecified vulnerability that allows for information disclosure.

Product: Android Framework · Assigned by: google_android · Published: 2025-12-08

Affected and fixed versions

VendorProductAffected versions (per CVE record)
GoogleAndroid16, 15, 14, 13

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.15.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
  • Attack vector: local access needed
  • Attack complexity: low
  • Privileges required: low (any account)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: added 2025-12-02; federal due date 2025-12-23. Known ransomware use: Unknown.
  • 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.
  • CISA SSVC assessment: exploitation active, automatable no, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.26% probability of exploitation activity in the next 30 days; percentile 17.

Timeline

  • — Added to CISA’s Known Exploited Vulnerabilities catalog
  • — CVE record published by google_android
  • — CISA remediation deadline for US federal agencies
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. Listed in CISA KEV notes (source.android.com) source.android.com

Vulnerability records

  1. CVE.org record CVE-2025-48633 cve.org
  2. NVD entry CVE-2025-48633 nvd.nist.gov

Government

  1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

  1. android.googlesource.com android.googlesource.com
  2. source.android.com source.android.com

All exploited Android vulnerabilities · Today’s Security Digest