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

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

How to fix or mitigate CVE-2025-48611?

Within 24 hours: Identify all systems running affected DeviceId.java versions and assess exposure scope; disable or restrict local access where feasible. Within 7 days: Implement compensating controls (network segmentation, enhanced access logging); communicate with vendor for patch timeline and workarounds. Within 30 days: Develop and execute remediation plan; apply vendor patch immediately upon release; conduct post-patch validation and security reassessment.

CVE-2025-48611

CRITICAL

Classic Buffer Overflow (CWE-120)

2026-03-10 security@android.com

Privilege Escalation Buffer Overflow

10.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Mar 10, 2026 - 20:16 nvd

CRITICAL 10.0

DescriptionCVE.org

In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

AnalysisAI

Android DeviceId component has a CVSS 10.0 out-of-bounds write in persistence handling enabling device compromise.

Technical ContextAI

DeviceId.java in Android has a CWE-120 buffer overflow due to a missing bounds check that causes a desync in persistence, potentially leading to complete device compromise.