VulnerabilityPublished 4 Sep 2025Updated 26 Feb 2026

CVE-2025-0077: Google Android · Elevation of Privilege

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.0Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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

Disclosed: evidence found.
CVE published 4 Sep 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	Fixed in–

AI-suggested

To mitigate CVE-2025-0077, organizations and users should apply official security patches from Google as soon as they become available for Android 15 devices. Until patches are released, enforcing strict physical security controls to prevent unauthorized local access to devices is critical. Employing device encryption and strong authentication methods (e.g., biometrics combined with PIN) may reduce the risk of data exposure. Administrators should monitor device usage and audit access logs for suspicious activity. Additionally, disabling or restricting local debugging and developer options can reduce attack surface. For enterprise environments, mobile device management (MDM) solutions should enforce security policies that limit physical access and lock screen bypass attempts. Regularly updating devices to the latest Android security updates will help prevent exploitation of this and similar vulnerabilities.

Description

In multiple functions of UserController.java, there is a possible lock screen bypass due to a race condition. 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-0077 is a local elevation of privilege through lock screen bypass, which can compromise the confidentiality of user data on affected Android 15 devices. Attackers with physical or local access could exploit this vulnerability to access sensitive information without authentication, undermining device security. Although the integrity and availability of the system are not directly affected, the ability to bypass the lock screen can facilitate further attacks or unauthorized data access. Organizations relying on Android 15 devices, especially in environments where devices are shared or physically accessible by untrusted individuals, face increased risk of data leakage or unauthorized access. The lack of required user interaction and no need for prior privileges lowers the barrier for exploitation, making it a concern for enterprise mobile security. However, the absence of known exploits in the wild and the medium CVSS score suggest the threat is moderate but should not be ignored.

CWE-1223Race Condition for Write-Once Attributes (opens in a new tab)
Base weakness
A write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race condition issue.
Architecture and Design
During hardware design, all register write-once or sticky fields must be evaluated for proper configuration.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 22:03 UTC

WeaknessesCWE-1223

Technical details

References

Community reviews

Related threats