Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-48595: Android Framework Integer Overflow Privilege Escalation

Published Jun 1, 2026 · Updated 20 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.4High · v3.1
EPSS2.0%81st percentile
CISA KEVYesAdded Jun 2, 2026
In the wildActivePer CISA KEV
Vendor
Google
IdentifiersCVE-2025-48595CWE-190 · Integer Overflow or Wraparound

CVE-2025-48595 is an integer overflow vulnerability affecting multiple locations in the Android Framework on Android 14, 15, 16, and Android 16 QPR2. A local attacker can exploit the flaw to execute arbitrary code and escalate privileges without additional execution privileges or user interaction. Specific vulnerable functions and triggering inputs have not been disclosed. The vulnerability is rated high severity with a CVSS score of 8.4, and Google has indicated limited, targeted exploitation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise operating-system privilege boundaries, allowing attacker-controlled code to run with elevated privileges. This may expose sensitive device data, credentials, and authentication tokens, potentially enabling unauthorized access to enterprise applications, corporate email, and VPN services accessible from the compromised device. The precise execution context and resulting privilege level are not specified.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict installation from unverified application sources, enable Google Play Protect, and audit installed applications for untrusted software. Temporarily restrict unpatched devices from accessing sensitive corporate systems. These measures reduce exposure but do not correct the integer overflow. Discontinue use of affected devices if vendor fixes or effective mitigations are unavailable.

Remediation

Patch, then assume compromise.

Install the device manufacturer's security update incorporating the June 2026 Android Framework fix. Core Framework fixes are included in security patch level 2026-06-01; security patch level 2026-06-05 or later includes those fixes plus additional June kernel and chipset updates and is the recommended deployment baseline. Use MDM or EMM controls to enforce updates and verify patch compliance across affected devices.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-48595-ExploitThis repository is a small Android proof-of-concept app for CVE-2025-48595. It is not part of a common exploit framework. The repository contains a standard Gradle Android project with one primary Java source file, AndroidManifest metadata, minimal resources, and a GitHub Actions workflow that builds a debug APK. The core exploit logic is entirely in app/src/main/java/com/cve202548595/MainActivity.java. When launched, the app starts a background thread that enumerates several Binder-exposed Android system services: activity, package, window, notification, power, and alarm. For each service, it uses reflection to call android.os.ServiceManager.getService(), obtains an IBinder handle, performs repeated one-way transactions that appear intended to shape heap/layout state, and then sends crafted Parcel payloads containing suspicious integer values (0x40000001, 0x80000001, 0x20000003) across transaction codes 1 through 20. The exploit treats a DeadObjectException as evidence that system_server crashed, which is its primary success condition. Capabilities are limited to local exploitation from an installed Android app. There is no remote C2, no network beaconing, no persistence, and no post-exploitation payload beyond attempting denial-of-service against privileged Android services/system_server. The app also reads /proc/self/attr/current to log its SELinux context, likely to help the operator understand the execution environment. Repository structure is straightforward: build.gradle and app/build.gradle define the Android build; AndroidManifest.xml declares a debuggable launcher activity; strings.xml contains only the app name; .github/workflows/build.yml automates APK compilation and artifact upload. Overall, this is a focused Binder IPC crash PoC intended to validate or demonstrate a local Android vulnerability rather than provide a full exploitation chain.XiaoBaiLovesStirring · Disclosed Aug 24, 2026 · java · groovy · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system
FAQ

Frequently asked questions

Is CVE-2025-48595 exploited in the wild?
Yes. As of Oct 28, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jun 2, 2026.
Is there a public exploit for CVE-2025-48595?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-48595, the earliest disclosed Aug 24, 2026.
Is there a patch for CVE-2025-48595?
Install the device manufacturer's security update incorporating the June 2026 Android Framework fix. Core Framework fixes are included in security patch level 2026-06-01; security patch level 2026-06-05 or later includes those fixes plus additional June kernel and chipset updates and is the recommended deployment baseline.
What products are affected by CVE-2025-48595?
Google Android.
How severe is CVE-2025-48595?
CVE-2025-48595 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 2.0% (81st percentile) as of Oct 28, 2026.
Activity feed

Recent activity

141 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+18 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity114Community discussion across Reddit, Mastodon, and other social sources.