Android · Framework · Android Framework Information Disclosure Vulnerability
Verdict
Patch on your normal cycle · actively exploited, not reachable unauthenticated from the internet, and in the upper half of CVEs by near-term exploitation probability
Added to CISA KEV 2025-12-02 · exploited in the wild for 299 days
CVSS 5.5 MEDIUM. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.
| Attack vector | localrequires local access to the machine |
|---|---|
| Privileges required | lowneeds some credentials, so a fully anonymous attacker cannot reach it directly |
| User interaction | nonecan be triggered with nobody interacting with the page or request |
| Base vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
This describes the vulnerability. It says nothing about whether your systems run it.
EPSS puts the probability of exploitation in the next 30 days at 0.0026, which places it in the upper half of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.
| EPSS probability | 0.0026 |
|---|---|
| Percentile | 0.162 — upper half |
| Added to KEV | 2025-12-02 |
|---|---|
| Days exploited | 299 |
| Federal remediation due | not set |
| Ransomware use | no known ransomware campaign use |
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
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.