VulnerabilityPublished 8 Dec 2025Updated 26 Feb 2026

CVE-2025-32329: 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, 14:05 UTC

CVSS 3.1 base score

7.8High

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

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
Google Android	Affected =15 =14 =13	Fixed in–

AI-suggested

1. Apply official security patches from Google as soon as they become available for Android versions 13, 14, and 15. 2. Enforce strict local device access controls, including strong authentication mechanisms (PIN, password, biometrics) to prevent unauthorized local access. 3. Limit the number of users and profiles on shared devices to reduce exposure. 4. Use device management solutions to monitor and restrict local user activities where feasible. 5. Educate users about the risks of sharing devices and the importance of separate user profiles with appropriate permissions. 6. Temporarily disable or restrict access to sensitive media files for secondary users until patches are applied. 7. Monitor device logs for unusual access patterns or privilege escalations. 8. For organizations, consider deploying endpoint detection and response (EDR) tools capable of detecting local privilege escalation attempts. 9. Encourage users to keep their devices updated regularly and avoid installing untrusted applications that could facilitate local attacks. 10. If possible, isolate sensitive workloads or data on dedicated devices not shared among multiple users.

Description

In multiple functions of Session.java, there is a possible way to view images belonging to a different user of the device 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-32329 is unauthorized access to private images of other users on the same Android device, violating confidentiality. This can lead to privacy breaches, data leakage, and potential misuse of sensitive media. The elevation of privilege aspect means an attacker with local access can gain higher privileges than intended, potentially allowing further compromise of the device. Integrity is also at risk if the attacker modifies or deletes images belonging to other users. Availability could be affected if the attacker disrupts access to user data or causes system instability. Organizations relying on Android devices for sensitive operations or storing confidential information face increased risk of insider threats or malicious local users exploiting this vulnerability. The lack of required user interaction and low complexity of exploitation increase the likelihood of successful attacks in shared device scenarios, such as corporate or family environments. The widespread use of affected Android versions globally amplifies the potential impact, especially in regions with high smartphone penetration and multi-user device usage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats