Quick answers
- Is CVE-2025-48595 exploited in the wild?
- Yes. CVE-2025-48595 is known to be exploited in the wild, first recorded on 2 June 2026. Treat it as urgent.
- How severe is CVE-2025-48595?
- Critical severity, with a CVSS score of 7.8, published 1 June 2026.
- Which products and versions are affected?
- Google Android Framework 14, 15, 16, 16-qpr2.
- Is there a fix for CVE-2025-48595?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-48595 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2025-48595?
- Check whether you run Android Framework or Google Android Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow vulnerability exists in multiple locations within the Android Framework. The flaw allows a local attacker to achieve arbitrary code execution without requiring additional execution privileges or user interaction. By exploiting this memory safety issue, an attacker can escalate their privileges to a higher level (such as system or root). The vulnerability was disclosed in the June 2026 Android Security Bulletin and is confirmed to have been exploited in the wild. Security updates are typically delivered via the Android Open Source Project (AOSP) and device manufacturer patches.
Affected products
- Google Android Framework
Timeline
- 2026-06-01: advisory: Vulnerability included in Android Security Bulletin
- 2026-06-02: disclosed: NVD publication date
- 2026-06-02: exploited: Reported as exploited in the wild in the advisory summary