Vulnerability record · CVE-2025-48595 · published 1 June 2026
CVE-2025-48595: Android Framework integer overflow enables local code execution
Google · Android
An integer overflow in multiple locations of the Android Framework can be turned into code execution. It allows a local attacker to escalate privileges without needing any additional execution privileges, and no user interaction is required. Because it is in the core framework and is listed in CISA KEV, it matters for any Android device that has not received the June 2026 bulletin fixes.
Description
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:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Automated analysis
high priorityIt is in CISA KEV with a short remediation deadline and gives local privilege escalation to code execution, though exploitation requires local access and EPSS is low.
What it is
An integer overflow in multiple locations of the Android Framework can be turned into code execution. It allows a local attacker to escalate privileges without needing any additional execution privileges, and no user interaction is required. Because it is in the core framework and is listed in CISA KEV, it matters for any Android device that has not received the June 2026 bulletin fixes.
Impact
An attacker who can run code on the device gains elevated privileges, potentially reaching system-level execution. The CVSS vector shows high confidentiality, integrity and availability impact, so full compromise of the affected component is possible.
Attack surface
The vector is local (AV:L) with no privileges (PR:N) and no user interaction (UI:N), so the flaw is reached by code already running on the device rather than over the network. No authentication or victim action is needed beyond local execution.
Exploitation
CVE-2025-48595 was added to CISA KEV on 2026-06-02 with a 2026-06-05 due date, indicating known exploitation. EPSS is low at roughly 1.7 percent (76th percentile), and no ransomware use is documented.
What to do
- Apply the June 2026 Android security bulletin fixes from Google as the first action.
- If patching is not immediately possible, follow CISA BOD 22-01 guidance and vendor mitigations, or discontinue use of affected devices.
- Restrict the ability to run untrusted local code on affected devices, for example by limiting sideloaded apps and untrusted build environments.
- Track device fleet patch status against the vendor bulletin and prioritize unpatched units.
- Monitor vendor channels for updated guidance if the bulletin is revised.
Detection
- Monitor for unexpected privilege escalation or anomalous system-level process behavior on Android devices.
- Audit which apps and processes can execute local code on managed devices and flag untrusted sources.
- Correlate device logs with the vendor bulletin patch level to find unpatched endpoints.
- Watch for post-exploitation activity consistent with local privilege escalation, such as new system-level processes or modified framework components.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2025-48595 to the Known Exploited Vulnerabilities catalog on 2 June 2026 as "Android Framework Integer Overflow Vulnerability". 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. Federal deadline 5 June 2026.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://source.android.com/docs/security/bulletin/2026/2026-06-01 | Vendor Advisory |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48595 | US Government Resource |
Track CVE-2025-48595 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2025-48595), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.