HIGH · CVSS 8.4 CISA Known Exploited Vulnerability

CVE-2025-48595

Android Framework Integer Overflow Vulnerability

Android Framework

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.

CVSS
8.4
HIGH
EPSS
1.7%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
1 Jun 2026
CWE-190

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 June 2026. US federal agencies were required to remediate it by 5 June 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 1.7%, which is higher than 75.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2025-48595 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-48595.

What does CVE-2025-48595 affect?

CVE-2025-48595 affects Android Framework. 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.

How severe is CVE-2025-48595?

CVE-2025-48595 is rated HIGH with a CVSS base score of 8.4. EPSS puts the probability of exploitation in the next 30 days at 1.7%, higher than 75.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 5 June 2026.

How should organisations respond to CVE-2025-48595?

Apply the vendor patch for Android Framework as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.