CVE-2025-48595: Android Framework Integer Overflow
Android Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2026-06-02.
- CVSS v3.1 (CISA ADP)
- 8.4
- high
- EPSS (exploit probability, 30 days)
- 2.0%
- higher than 81.2% of all CVEs
- Added to CISA KEV
- 2026-06-02
- US federal due date 2026-06-05
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-48595 explained
CVE-2025-48595 is an integer overflow in the Android Framework that can allow code execution in multiple locations. It can lead to local escalation of privilege without additional execution privileges or user interaction. CISA lists it as known to be exploited, so affected Android devices should be patched with priority.
Impact
An attacker with local access can trigger the integer overflow to execute code and escalate privileges on the device. No privileges and no user interaction are required, and attack complexity is low. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected component, but not automatable, so exploitation is not expected to scale without manual steps. Attackers are known to exploit it.
Who is affected
The CVE record lists Google Android versions 14, 15, 16 and 16-qpr2 as affected. The record names no fixed version. Check the vendor advisory for the security patch level that addresses this vulnerability on each affected release.
Written with AI from the data on this page and checked against it automatically.
Official 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.
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 notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google AndroidAffectedFixed in
- 14
- 15
- 16
- 16-qpr2
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Google Android |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: source.android.com/docs/security/bulletin/2026/2026-06-01
- CISA's deadline for US federal agencies: 2026-06-05 (passed) – a useful benchmark for everyone else, too.
What to do
- Review the Android vendor advisory to identify the security patch level that fixes CVE-2025-48595.
- Install the corresponding Android security update on all devices running
14,15,16or16-qpr2. - Use device management tooling to enforce the minimum patch level and flag non-compliant devices.
- Apply mitigations per vendor instructions, or discontinue use of devices if mitigations are unavailable, as CISA requires.
- Limit installation of untrusted apps and check managed devices for signs of compromise.
The CVE record names no fixed version, which does not mean no fix exists. Follow the vendor advisory to find the relevant Android security update. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Restrict untrusted apps on affected devices until updates are confirmed installed.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-190 Integer Overflow or Wraparound
Questions about CVE-2025-48595
- Is CVE-2025-48595 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-06-02, with a US federal due date of 2026-06-05. Whether it is used in ransomware campaigns is unknown.
- Does exploitation require user interaction?
- No. The description states user interaction is not needed, and no additional execution privileges are required. The attack vector is local.
- Which Android versions are affected?
- The CVE record lists Google Android
14,15,16and16-qpr2. It names no fixed version, so consult the vendor advisory for the correct security patch level.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.