Google Patches Actively Exploited Android Zero-Day (CVE-2025-48595) in June Security Update

Android Zero-Day Under Attack: Google Issues Urgent Patch for Privilege Escalation Flaw

HIGH
June 2, 2026
June 6, 2026
m read
VulnerabilityMobile SecurityPatch Management

Related Entities(initial)

Organizations

GoogleQualcomm

Products & Tech

Android

CVE Identifiers

CVE-2025-47392
CRITICAL
CVE-2025-48595
HIGH
CVE-2025-65018
CRITICAL
CVE-2026-0043
CRITICAL
CVE-2026-0097
CRITICAL
CVE-2026-21352
CRITICAL
CVE-2026-21353
CRITICAL
CVE-2026-25276
CRITICAL
CVE-2026-25277
CRITICAL

Full Report(when first published)

Executive Summary

Google has released its June 2026 security update for the Android operating system, patching a total of 124 vulnerabilities. The most critical fix addresses CVE-2025-48595, a high-severity Elevation of Privilege (EoP) vulnerability in the Android Framework that is being actively exploited in the wild. Google has confirmed the flaw is subject to "limited, targeted exploitation." A successful attack could allow a malicious application to gain system-level privileges, completely compromising the security of the device. The update also includes patches for 18 other critical vulnerabilities. Due to the active exploitation, users are strongly advised to apply the June 2026 security patch as soon as their device manufacturer makes it available.


Vulnerability Details

The primary vulnerability of concern is:

  • CVE-2025-48595: An Elevation of Privilege (EoP) vulnerability in the Android Framework. This is a high-severity flaw that requires a local attacker (e.g., a malicious app installed by the user) to exploit. Successful exploitation allows the attacker to escalate their privileges, potentially to the level of the operating system (SYSTEM), enabling them to bypass Android's security model, access sensitive data, and execute arbitrary code.

Google has not disclosed technical details about the vulnerability or the nature of the in-the-wild attacks to prevent wider exploitation. Such zero-day flaws are frequently used by commercial spyware vendors and nation-state actors for targeted surveillance.

Other Critical Vulnerabilities

The June 2026 bulletin also addresses several other critical flaws, including:

  • CVE-2025-65018: A critical remote privilege escalation flaw, also in the Framework component, which could be exploited without user interaction.
  • Multiple critical flaws in the System component and Qualcomm closed-source components that could lead to privilege escalation or remote code execution.

Affected Systems

  • Actively Exploited Flaw (CVE-2025-48595): Affects Android versions 14, 15, and 16.
  • Other Vulnerabilities: Affect a wide range of Android OS versions and components.

The update is being delivered in two patch levels:

  • 2026-06-01: Addresses vulnerabilities in core Android components.
  • 2026-06-05: A comprehensive patch level that includes the 2026-06-01 fixes plus patches for third-party and kernel components.

Google Pixel devices are typically the first to receive these updates, with other manufacturers like Samsung, OnePlus, and others following over the subsequent weeks and months.


Exploitation Status

Active Exploitation Confirmed. Google's bulletin explicitly states there are "indications that CVE-2025-48595 may be under limited, targeted exploitation." This elevates the urgency of patching significantly. While the scope is described as "limited," any actively exploited zero-day poses a serious threat.

MITRE ATT&CK Techniques


Impact Assessment

A successful exploit of CVE-2025-48595 could have severe consequences for an affected user. An attacker with system-level privileges can:

  • Access all data on the device, including emails, messages, photos, and banking app data.
  • Bypass all application sandboxing and permissions.
  • Install persistent malware or spyware that survives a reboot.
  • Activate the microphone and camera to spy on the user.
  • Steal credentials stored on the device.

Given that the exploitation is targeted, the immediate risk to the general population is lower than a widespread attack. However, the existence of the exploit means it could be incorporated into more widely distributed malware in the future.


Cyber Observables — Hunting Hints

Detection on an individual mobile device is difficult for end-users. For enterprise mobile device management (MDM) platforms, the following patterns could indicate a compromise:

Type
process_name
Value
Unexpected processes running as system or root
Description & Context
Monitor for processes that are not part of the standard Android OS running with elevated privileges.
Type
network_traffic_pattern
Value
Unexplained data exfiltration
Description & Context
An app with no reason to upload large amounts of data suddenly sending traffic to an unknown server.
Type
log_source
Value
Android System Logs (logcat)
Description & Context
Look for crash reports or security exceptions related to the Android Framework that coincide with the installation of a new app.
Type
other
Value
Device running an outdated security patch level
Description & Context
The most reliable indicator of risk is an unpatched device. Use MDM to enforce patch compliance.

Detection Methods

For most users, detection is not feasible. The focus should be on prevention and remediation.

  • Mobile Device Management (MDM): Enterprises should use MDM solutions to query the security patch level of all managed Android devices. Create policies to alert on or restrict access for devices that have not been patched within a defined timeframe.
  • Mobile Threat Defense (MTD): MTD solutions can provide more advanced detection by monitoring device behavior, network traffic, and application integrity to identify signs of compromise that may result from exploiting this vulnerability.
  • App Vetting: Only install applications from the official Google Play Store. While not a perfect defense, it significantly reduces the risk of installing malicious apps that could exploit this flaw.

Remediation Steps

  1. Update Immediately: The only effective remediation is to install the June 2026 Android security update. Users should navigate to Settings > System > System update (or similar path depending on the manufacturer) to check for and apply the update.
  2. Reboot Device: After the update is installed, reboot the device to ensure all patched components are loaded correctly.
  3. Practice App Hygiene: Regularly review installed applications and remove any that are not needed or from untrusted sources. Be cautious about granting permissions to applications.

Timeline of Events

1
June 2, 2026
Google releases the June 2026 Android Security Bulletin, acknowledging active exploitation of CVE-2025-48595.
2
June 2, 2026
This article was published

Article Updates

June 3, 2026

Severity increased

New details emerge on Android's June 2026 update, clarifying CVE-2025-65018 as a critical, potentially wormable RCE, and listing additional CVEs.

The June 2026 Android security update now includes clarified details on CVE-2025-65018, identifying it as a critical Remote Code Execution (RCE) vulnerability in the Android Framework. This flaw is highlighted as potentially wormable, allowing remote attackers to execute arbitrary code without user interaction, significantly increasing its risk profile. Additionally, specific CVEs for other critical local privilege escalation flaws (e.g., CVE-2026-0043, CVE-2026-21352) and a Qualcomm memory corruption vulnerability (CVE-2026-21385) have been disclosed. The report also incorporates D3FEND and MITRE M1017 for enhanced detection and mitigation strategies.

June 6, 2026

Severity increased

CISA adds Android zero-day (CVE-2025-48595) to KEV catalog, mandating federal agency patching. New details reveal it's an integer overflow with CVSS 8.4.

The actively exploited Android zero-day, CVE-2025-48595, is now confirmed to be an integer overflow vulnerability in the Android Framework, carrying a high CVSS score of 8.4. This flaw allows for local privilege escalation without user interaction, affecting Android versions 14, 15, 16, and 16 QPR2. A significant development is CISA's addition of this CVE to its Known Exploited Vulnerabilities (KEV) catalog, which mandates federal agencies to patch by June 5, 2026. This highlights the critical nature and active threat posed by the vulnerability, reinforcing the urgency for all users to apply the June 2026 security update.

Timeline of Events

1
June 2, 2026

Google releases the June 2026 Android Security Bulletin, acknowledging active exploitation of CVE-2025-48595.

Sources & References(when first published)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

AndroidCVE-2025-48595GoogleMobile SecurityPatch TuesdayPrivilege EscalationZero-Day

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.