What is the CVSS score of CVE-2025-48568?

CVE-2025-48568 has a CVSS 3.1 base score of 7.4 (High). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Android are affected by CVE-2025-48568?

A race condition vulnerability in the lockscreen mechanism allows local attackers to bypass authentication and gain unauthorized device access without requiring special privileges.

How to fix or mitigate CVE-2025-48568?

Within 24 hours: Inventory all affected devices and assess exposure based on physical access risk in your environment. Within 7 days: Communicate vulnerability status to device users and management; implement enhanced physical security controls for high-risk areas. Within 30 days: Establish daily monitoring for vendor patch release; prepare deployment procedures for immediate rollout once available; evaluate alternative endpoint protection solutions if patch delays extend beyond 60 days.

Android CVE-2025-48568

HIGH

Race Condition (CWE-362)

2026-03-02 security@android.com

Privilege Escalation Google Race Condition Android

7.4

CVSS 3.1

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Mar 02, 2026 - 19:16 nvd

HIGH 7.4

DescriptionNVD

In multiple locations, there is a possible lockscreen 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.

AnalysisAI

In multiple locations, there is a possible lockscreen bypass due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. [CVSS 7.4 HIGH]

Technical ContextAI

Classified as CWE-362 (Race Condition). Affects Android. In multiple locations, there is a possible lockscreen 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.