SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2025-48633Public Intelligence Dossier
Source: google · Limited verification•Last verified: •Collection Degraded
CVE-2025-48633ListedMEDIUM (raw)CVSS 5.5NVD-CWE-noinfo

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

Published: 08 Dec 2025•Last updated: 08 Oct 2026, 01:40 AM IST•Source identifier: security@android.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added02 Dec 2025
Due23 Dec 2025
RansomwareUnknown
CVSS score
5.5MEDIUM (raw)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Metric sourcenvd@nist.gov
EPSS probability
0.3%0.003
Percentile18th
Weakness type
NVD-CWE-noinfo
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • google android · 13.0; 14.0; 15.0; 16.0 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
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.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched local-access-review (CVSS AV:L, CVSS PR:L)

Exposure

  1. Identify hosts reporting this CVE, prioritising shared or multi-user systems.Telemetry: DeviceTvmSoftwareVulnerabilities · A local, low-privilege vector matters most where untrusted users can run code. · Rule local-access-review

Exploitation evidence

  1. Review source-stated impact and relevant application errors on affected hosts; local access alone does not establish privilege escalation.Telemetry: DeviceProcessEvents · The vector establishes local access and low privileges only. Confirm the impact from the advisory before choosing a specific hunt. · Rule local-access-review

Response

  1. Confirm the source-stated update on affected hosts.Telemetry: DeviceTvmSoftwareVulnerabilities · Host inventory can verify remediation. · Rule local-access-review

CISA KEV Record

Catalog entry
02 Dec 2025
Required action due
23 Dec 2025
Known ransomware use
Unknown

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
security@android.com
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*, cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*, cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*, cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2025-48633
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2025-48633
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2025-48633"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.