CVE-2025-48633VulnerabilityPublished 8 Dec 2025Updated 26 Feb 2026

CVE-2025-48633: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

Exploited in the wild · KEV due 23 Dec 2025 : apply the vendor's fix or mitigations to Google Android now.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 23 Dec 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 8 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 6 days before disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by google_android
2025-05-2218:12Z, 200 days before disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2025-12-02, 6 days before disclosure
CVE published
on cve.org
2025-12-0816:57Z, t = 0
In Threat Radar
record ingested
2025-12-0817:06Z, 8 minutes after disclosure
KEV remediation due
US federal deadline
2025-12-23, 15 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Affected software

Product	Affected	Fixed in
Google Android	Affected =16 =15 =14 =13	Fixed in–

Description

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.

Impact

The primary impact of CVE-2025-48633 is local privilege escalation on affected Android devices, allowing an attacker with limited privileges to gain Device Owner status post-provisioning. This elevated privilege can expose sensitive device management information and potentially allow unauthorized changes to device policies. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach can lead to further attacks or unauthorized access to corporate or personal data managed by device policies. Organizations relying on Android devices for enterprise mobility management or government use may face increased risk of insider threats or malware leveraging this flaw to bypass security controls. Since no user interaction is required, exploitation can occur silently once local access is obtained, increasing the risk in shared or physically accessible devices. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability's nature suggests it could be leveraged in targeted attacks against high-value Android deployments.

Mitigation

To mitigate CVE-2025-48633, organizations should implement the following specific measures: 1) Restrict physical and local access to Android devices, ensuring only trusted users can interact with them. 2) Monitor and audit device owner assignments and provisioning logs to detect unauthorized changes. 3) Apply security policies that limit the ability to add or modify device owners post-provisioning, if configurable via MDM solutions. 4) Deploy endpoint detection and response (EDR) tools capable of identifying anomalous privilege escalations on Android devices. 5) Stay informed about official Google security advisories and apply patches promptly once available. 6) Consider using device encryption and strong authentication mechanisms to reduce the risk of local exploitation. 7) Educate users and administrators on the risks of local privilege escalation and enforce strict device usage policies. These steps go beyond generic advice by focusing on controlling local access, monitoring device owner changes, and preparing for patch deployment.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 05:24 UTC

Technical details

References

Community reviews

Related threats