Security Digest · Vulnerability record · Known exploited

CVE-2025-48595: Android Framework Integer Overflow Vulnerability

Exploited in the wild (CISA KEV). In multiple locations, there is a possible way to achieve code execution due to an integer overflow.

CISA KEV · added 2026-06-02 CVSS 8.4 High EPSS 1.7% · p77

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Yes, if you run Android Framework. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-06-02, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-06-05; treat that as the outer limit, not the target.
  • EPSS 1.7%, percentile 77: FIRST’s model estimates a 1.7% chance of exploitation activity in the next 30 days, higher than 77% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.

What it is

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.

CISA’s summary

Android Framework contains an integer overflow vulnerability that allows for code execution that could allow for local privilege escalation.

Weakness type: CWE-190.

Product: Android Framework · Assigned by: google_android · Published: 2026-06-01

Affected and fixed versions

VendorProductAffected versions (per CVE record)
GoogleAndroid16-qpr2, 16, 15, 14

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.18.4 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: local access needed
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: added 2026-06-02; federal due date 2026-06-05. Known ransomware use: Unknown.
  • CISA 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.
  • CISA SSVC assessment: exploitation active, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 1.71% probability of exploitation activity in the next 30 days; percentile 77.

Timeline

  • — CVE record published by google_android
  • — Added to CISA’s Known Exploited Vulnerabilities catalog
  • — CVE record last updated
  • — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. Listed in CISA KEV notes (source.android.com) source.android.com

Vulnerability records

  1. CVE.org record CVE-2025-48595 cve.org
  2. NVD entry CVE-2025-48595 nvd.nist.gov

Government

  1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

All exploited Android vulnerabilities · Today’s Security Digest