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

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

How to fix or mitigate CVE-2025-48653?

Within 24 hours: Identify all affected systems running vulnerable versions and document their business criticality. Within 7 days: Implement compensating controls including restricting local administrative access, enforcing strict access controls on affected applications, and monitoring for suspicious privilege escalation attempts. Within 30 days: Establish a continuous monitoring program for patch availability and prepare a rapid deployment plan; consider temporary feature disablement if the vulnerable functionality is non-critical.

Android CVE-2025-48653

HIGH

Protection Mechanism Failure (CWE-693)

2026-03-02 security@android.com

Privilege Escalation Google Android

7.8

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-693 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V15 - Secure Coding and Architecture Protection mechanism completeness
Impact	CVSS 7.8 (HIGH). Attack vector: Local. Complexity: Low. Privileges required: Low. User interaction: None. Exploitable via local access.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to local escalation of privilege with no additional execution privileges needed.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

In loadDataAndPostValue of multiple files, there is a possible way to obscure permission usage due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. [CVSS 7.8 HIGH]

RemediationAI

Monitor vendor advisories for a patch.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-693 (Protection Mechanism Failure). Affects Android. In loadDataAndPostValue of multiple files, there is a possible way to obscure permission usage 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.

Know when Android gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

Executive ViewAI

Why It Matters

CVE-2025-48653 is a privilege escalation vulnerability affecting multiple applications that could allow local attackers to bypass permission controls and gain unauthorized elevated access. This poses a significant risk to organizations where users have local system access, as attackers could exploit this to access sensitive data or critical systems without requiring additional privileges.

Business Impact: High

Compensating Controls

Restrict local system access to trusted users only; implement application-level access controls to limit permission usage; deploy behavioral analytics to detect abnormal privilege escalation attempts; consider disabling the affected loadDataAndPostValue functionality if not business-critical; isolate affected systems from sensitive data and critical resources through network segmentation; enforce enhanced logging and audit trails on affected applications.

Threat Intelligence Overview

EPSS Score

0.0%

Top 99% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Small

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +39

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Privilege Escalation HIGH

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.