CVE-2025-48595

Exp

In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Published: 2026-06-01 Last update: 2026-06-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-48595 is rated Critical Active Threat (82.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.53%). CISA KEV confirms active exploitation (added 2026-06-02) affecting Android / Framework. a weakness (CWE-190) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2025-48595

Name: Android Framework Integer Overflow Vulnerability · CISA KEV detail

Exploit added: 2026-06-02

Action due: 2026-06-05

Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Exploit prediction scoring system (EPSS) score for CVE-2025-48595

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-07 0.40% 0.53% +0.13%
2 2026-06-03 0.01% 0.40% +0.39%
3 2026-06-02 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-48595

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.4 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.5 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-48595

GitHub Security Advisory for CVE-2025-48595

GHSA-2mvq-m5m5-v7m7 · Severity: high — In multiple locations, there is a possible way to achieve code execution due to an integer...

Affected software / configurations for CVE-2025-48595

Vendor Product Version Raw CPE
google android 14.0 cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
google android 15.0 cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*
google android 16.0 cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:*
google android 16.0 cpe:2.3:o:google:android:16.0:qpr2_beta_1:*:*:*:*:*:*
google android 16.0 cpe:2.3:o:google:android:16.0:qpr2_beta_2:*:*:*:*:*:*
google android 16.0 cpe:2.3:o:google:android:16.0:qpr2_beta_3:*:*:*:*:*:*

References for CVE-2025-48595

cvelogic Threat Intelligence