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

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

Which versions of Google are affected by CVE-2025-48564?

CVE-2025-48564 presents moderate security risk, a race condition vulnerability rated CVSS 7.0. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2025-48564?

Within 7 days: Identify all affected systems and apply vendor patches promptly. Vendor patch is available.

Google CVE-2025-48564

EUVD-2025-201779 HIGH

Race Condition (CWE-362)

2025-12-08 security@android.com

Privilege Escalation Google Race Condition

7.0

CVSS 3.1 · Vendor: android

Severity by source

Vendor (android) PRIMARY

7.0 HIGH

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

Primary rating from Vendor (android) · only source for this CVE.

CVSS VectorVendor: android

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 15, 2026 - 17:54 euvd

EUVD-2025-201779

Analysis Generated

Mar 15, 2026 - 17:54 vuln.today

Patch released

Mar 15, 2026 - 17:54 nvd

Patch available

CVE Published

Dec 08, 2025 - 17:16 nvd

HIGH 7.0

DescriptionCVE.org

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

Analysis

Technical ContextAI

A race condition occurs when the behavior of software depends on the timing of events, such as the order of execution of threads or processes.

RemediationAI

A vendor patch is available — apply it immediately. Use proper synchronization mechanisms (locks, mutexes, atomic operations). Implement file locking for filesystem operations. Avoid TOCTOU patterns.