Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2025-48633
CVE-2025-48633
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- Dec 8, 2025
- Updated
- Feb 26, 2026
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 16.2%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
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.
Android Framework Information Disclosure Vulnerability
Probability 0.002490000000; percentile 0.162340000000
Applicability
Cited product scope
[{"status": "affected", "version": "16"}, {"status": "affected", "version": "15"}, {"status": "affected", "version": "14"}, {"status": "affected", "version": "13"}]unknowncpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*supportedcpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*supportedcpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*supportedcpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*supportedAssessments
CVSS by origin
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.