CriticalCVE-2025-48595

    Android Framework Integer Overflow Vulnerability (CVE-2025-48595)

    Published In CISA KEV since Sources: OSV, pwn.watch, CVE.org, BSI

    What is affected, what to do

    The vulnerability CVE-2025-48595 in the Android Framework allows for local privilege escalation due to an integer overflow. An attacker can execute code without additional privileges or user interaction, gaining control over the device. This vulnerability is actively exploited in the wild, as evidenced by its inclusion in the CISA KEV list. Affected products include various versions of the Android Framework, particularly in SQLite and release builds. An immediate update to the latest version is urgently required to mitigate this security risk.

    The vulnerability is being actively exploited; treat it as a priority. Update Android security patch level to version 2026-06-01, Android to version SMR-APR-2026, Android 13 to version SMR-NOV-2025. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Google Android eq 16-qpr2..16-qpr2
    • Google Android eq 16..16
    • Google Android eq 15..15
    • Google Android eq 14..14

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.4

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.4

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: OSV, pwn.watch, CVE.org, BSI

    2.0 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 80.1

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    211.61 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.4 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.4
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    2.0 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    80.1
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 1 June 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-190

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw grants local privilege escalation with no user interaction and no prior privileges — a classic stage in exploit chains where a malicious app or an upstream remote exploit gains full control of the device, and such chains are frequently aimed at selected individuals (executives, government staff, journalists, critical-infrastructure operators). Statistical exploitation likelihood is moderate and CISA reports no known ransomware use, but the impact of success is severe: complete loss of confidentiality, integrity and availability on the device, including MFA factors and corporate data. Organisations with large Android fleets, BYOD, or privileged users on mobile should enforce the update within their standard critical window, and treat high-exposure user groups immediately.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Establish patch posture: Use your MDM/UEM (Intune, Workspace ONE, Ivanti, Google Endpoint Management) to inventory every device running Android 14, 15, 16 and 16-QPR2 and export the reported Android security patch level. Treat these devices as vulnerable until the fix is verifiably installed.
      • Deploy the fix: The fix ships via the Android Security Bulletin and downstream OEM updates. Patch available from the vendor — look up the required security patch level in the Android Security Bulletin and the relevant OEM advisory (Samsung, Pixel, Zebra, etc.). Enforce installation through an MDM system-update policy rather than relying on user prompts.
      • Tighten compliance: Set the "minimum security patch level" in your compliance policy to the fixed level and use Conditional Access (or equivalent) to block non-compliant devices from mail, VPN, M365/Workspace and internal apps.
      • Prioritise high-value devices: Update devices belonging to admins, executives, OT/control-room staff, and any device holding MFA authenticators, certificates or privileged remote access first — or disconnect them from corporate resources until patched.
      • Handle suspected compromise: On indicators of exploitation (see detection), isolate the device, revoke session and refresh tokens, revoke device certificates, re-provision the user's MFA, and factory-reset the device rather than attempting to clean it.

    2. Runbook step 2

      Mitigation layers

      • Endpoint hardening / configuration: Via Android Enterprise policy, block installs from unknown sources, enforce Google Play Protect, and disable USB debugging and developer options. Exploitation is local, so malicious code on the device is the realistic prerequisite — controlling what gets installed cuts most of the risk.
      • App allowlisting: On fully managed devices, permit only approved apps from Managed Google Play; on BYOD, keep corporate data in the work profile and disable cross-profile copy/share.
      • Network segmentation: Place mobile devices in a dedicated Wi-Fi/VLAN segment with no direct reach to management interfaces, jump hosts or OT networks. Expose internal services only through per-app VPN or a ZTNA gateway that checks device health.
      • IAM / least privilege: Privileged accounts (domain/cloud admins) must not be used from mobile devices; restrict admin portals to managed desktop workstations via Conditional Access. Prefer phishing-resistant MFA (FIDO2 hardware keys) so a compromised phone does not automatically mean account takeover.
      • Lifecycle: Exclude devices whose OEM no longer ships security updates from corporate access and start replacement — without a vendor patch there is no complete mitigation.
      • Mobile Threat Defense: Where licensed (Defender for Endpoint on Android, Lookout, Zimperium, etc.), feed the MTD risk score into compliance and auto-block access at "high risk".

    3. Runbook step 3

      Detection rules

      • Patch-level drift (MDM/SIEM): Scheduled report of Android devices below the fixed patch level. KQL example (Defender XDR): DeviceInfo | where OSPlatform == "Android" | summarize arg_max(Timestamp, *) by DeviceId | project DeviceName, OSVersion, OSBuild, LoggedOnUsers — reconcile against the required patch level.
      • Integrity loss: Treat failed Play Integrity/device attestation, newly reported root status or an unlocked bootloader on previously clean devices as a high-priority alert (MDM compliance event "device rooted/compromised").
      • MTD/EDR alerts: Correlate alerts on privilege-escalation attempts, suspicious system processes, newly installed apps requesting device-admin or accessibility rights, and sideload events; Sigma shape: logsource: product=android, service=mtd | detection: event_type in (privilege_escalation, root_detected, sideload_install).
      • Identity anomalies: In Entra ID/IdP logs, hunt for token use tied to known mobile device IDs from unusual geolocations/ASNs, new MFA method registrations, or bulk mail/file access shortly after the device fell out of compliance.
      • Network telemetry: In Zeek/Suricata or proxy logs from the mobile segment, look for connections to newly registered domains, unusual upload volumes, or beaconing patterns (regular intervals, small payloads).

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: OSV (Open Source Vulnerabilities), pwn.watch, cvelistv5, CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), BSI CSAF, BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    GoogleAndroid
    • 16-qpr2
    • 16
    • 15
    • 14
    • —
    • —
    • —
    • —
    GoogleAndroid security patch level
    • < 2026-06-01
    • 2026-06-01
    SamsungAndroid
    • < SMR-APR-2026
    • SMR-APR-2026
    SamsungAndroid 13
    • < SMR-NOV-2025
    • SMR-NOV-2025
    SamsungAndroid 14
    • < SMR-NOV-2025
    • SMR-NOV-2025
    SamsungAndroid 15
    • < SMR-NOV-2025
    • SMR-NOV-2025
    SamsungAndroid 16
    • < SMR-NOV-2025
    • SMR-NOV-2025
    androidplatform/build/release
    • 16-qpr2:0
    • 16-qpr2
    • 15:0
    • 16
    • 16:0
    • 15
    • 16-qpr2:2026-06-01
    • —
    • 15:2026-06-01
    • —
    • 16:2026-06-01
    • —
    androidplatform/external/sqlite
    • 16:0
    • 14
    • 15:0
    • 16-qpr2:0
    • 16-qpr2
    • 17-next:0
    • 15
    • 14:0
    • 16
    • 17-next
    • 16:2026-06-01
    • —
    • 15:2026-06-01
    • 16-qpr2:2026-06-01
    • —
    • 17-next:2026-06-01
    • —
    • 14:2026-06-01
    • —
    • —
    androidplatform/vendor/google_shared/build/release
    • 15
    • 15:0
    • —
    • 15:2026-06-01

    Vendors and products

    Affected operating systems

    Affected operating systems
    Mobilegoogleandroid14.0
    Mobilegoogleandroid15.0
    Mobilegoogleandroid16.0

    Weakness classes (CWE)

    • CWE-190Integer Overflow or Wraparound

      Base

      The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

      Entry at MITRE CWE-190

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    PoC-in-GitHub (nomi-sec)CVE-2025-48595-Exploit (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-48595-Android-Framework-Integer-Overflow- (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-48595 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-48595
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-48595"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-48595.svg?lang=en" alt="CVE-2025-48595 – NEOSEC Intel" height="20"></a>