CVE-2025-48565VulnerabilityPublished 8 Dec 2025Updated 8 Sep 2026

CVE-2025-48565: Google Android · Elevation of privilege

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.8High

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% 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:H/A:H

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

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: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (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

Affected software

Product	Affected	Fixed in
GoogleAndroid	Affected =17 =16-qpr2 =16 =15 =14	Fixed in–

AI-suggested

To mitigate CVE-2025-48565 effectively, organizations and users should: 1) Apply official security patches from Google as soon as they become available to address the logic error in cross profile intent filters. 2) Restrict installation of apps from untrusted sources to reduce the risk of malicious local apps exploiting the vulnerability. 3) Enforce strict app permission policies, especially for apps requesting access to inter-profile communication or sensitive system functions. 4) Utilize mobile device management (MDM) solutions to monitor and control profile configurations and detect anomalous behavior indicative of privilege escalation attempts. 5) Educate users about the risks of installing unverified applications and the importance of device security hygiene. 6) Temporarily disable or limit use of multiple user profiles on Android devices in high-risk environments until patches are applied. 7) Monitor device logs and security alerts for suspicious local activity that could signal exploitation attempts. These steps go beyond generic advice by focusing on controlling local access vectors and profile management, which are directly relevant to this vulnerability's exploitation path.

Description

In multiple locations, there is a possible way to bypass the cross profile intent filter 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 impact of CVE-2025-48565 is substantial for organizations and individuals relying on Android devices, particularly those using multi-profile features such as work profiles. Successful exploitation allows local attackers to escalate privileges, potentially gaining access to sensitive data, modifying system settings, or installing persistent malware. This compromises confidentiality, integrity, and availability of the device and its data. For enterprises, this could lead to data breaches, unauthorized access to corporate resources, and disruption of mobile workforce operations. The vulnerability also increases the risk of lateral movement within devices, enabling attackers to bypass security controls designed to isolate user profiles. Since no user interaction is needed, exploitation can occur silently, making detection difficult. The requirement for local access limits remote exploitation but does not eliminate risk, as malicious apps or insiders could leverage this flaw. The absence of known exploits currently provides a window for mitigation, but the high severity score underscores the urgency for patching and protective measures.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats