Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious app to target device
-
DeliveryInstall app via sideload or compromised channel
-
ExploitCraft intent targeting SlicePermissionActivity onCreate
-
ExecutionTrigger confused deputy permission bypass
-
PersistObtain unauthorized slice access permissions
-
ImpactEscalate privileges on device
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires that the attacker control a low-privileged application already installed on the target Android device - this is the PR:L prerequisite in the CVSS vector and the binding local access constraint (AV:L). The confused deputy is triggered through a crafted intent directed at SlicePermissionActivity.java's onCreate method; no special system configuration or feature enablement beyond the default Android Slice framework is stated as a prerequisite. No user interaction is required after the malicious app is installed (UI:N). Exploitation is limited by: (1) the attacker must have a pathway to install an app on the target device, whether through physical access, social engineering to sideload, or a compromised distribution channel; (2) SSVC rates this as non-automatable, ruling out mass remote exploitation; (3) the attack is strictly local and cannot be triggered remotely without a prior installation-level foothold. |
| Impact | The CVSS 7.8 score with AV:L/PR:L is calibrated appropriately for a local Android LPE: network exploitation is not possible, and a malicious app must already be installed. EPSS at 0.12% (2nd percentile) indicates very low observed exploitation probability in the wild. SSVC corroborates this - Exploitation: none, Automatable: no - meaning mass or opportunistic remote exploitation is not feasible at this time. However, SSVC Technical Impact is rated 'total', consistent with the C:H/I:H/A:H vector: a successful exploit grants an attacker full control over the device's data, integrity, and availability. The breadth of affected versions (Android 14 through 17) is notably wide, covering the current production Android ecosystem and increasing aggregate exposure significantly. Even a mid-sized municipal IT team in sanok managing a fleet of Android devices should treat this as part of the standard September 2026 Android patch cycle rather than a deprioritized edge case. The low EPSS and absence from CISA KEV indicate this is not an actively weaponized threat, but the low exploitation complexity (AC:L, no UI) makes it a reliable escalation primitive for a targeted attacker who can install an app on the victim device. |
| Exploit ScenarioDerived | An attacker packages a malicious Android application and delivers it to a target device via sideloading, a third-party app store, or a compromised enterprise MDM channel. Once installed, the app sends a crafted intent to SlicePermissionActivity.java's onCreate handler, exploiting the confused deputy flaw to obtain slice access permissions it was not granted by the user. With these elevated permissions, the attacker's app can access data or functionality belonging to higher-privileged apps, effectively achieving local privilege escalation without requiring any further user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Local privilege escalation in Android's Slice permission subsystem allows a low-privileged installed application to bypass permission checks via a confused deputy flaw in SlicePermissionActivity.java's onCreate method. Affecting Android 14 through 17 (including the 16-QPR2 branch), the vulnerability requires no user interaction and grants full C:H/I:H/A:H impact on a successful device. No public exploit has been identified at time of analysis, and EPSS scoring (0.12%, 2nd percentile) reflects low current exploitation activity.
RemediationAI
Apply the September 2026 Android Security Bulletin patches (patch level 2026-09-01 or later), available at https://source.android.com/docs/security/bulletin/2026/2026-09-01, through OEM and carrier over-the-air update channels. Enterprise MDM administrators should enforce a minimum security patch level of 2026-09-01 across managed Android 14-17 device fleets and verify compliance via device attestation. No exact fixed build version is independently confirmed beyond the September 2026 bulletin date. Where immediate patching is not possible, restricting the installation of sideloaded or untrusted applications via Google Play Protect enforcement or MDM policy is the most actionable compensating control, as exploitation requires a malicious app to be present on the device. Disabling the Slice framework is not a practical standalone mitigation as it is a core Android system component and cannot be selectively disabled without vendor modification.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Android's Slice framework, introduced in Android 8.1, allows applications to expose interactive content templates ('slices') that other apps - such as the system launcher or Google Assistant - can render. SlicePermissionActivity.java is the system activity responsible for presenting the runtime permission grant dialog when one app requests slice access from another. CWE-441 (Confused Deputy) describes a scenario in which a legitimately privileged component - here, a system-level activity with permission-granting authority - can be tricked by an unprivileged caller into performing an action that the caller itself does not have the right to perform. The onCreate handler in this activity fails to adequately validate the caller's identity or intent before granting permissions, allowing a malicious app to impersonate a legitimate requestor. The CVSS vector AV:L/AC:L/PR:L/UI:N confirms local access and low-privilege prerequisites; no CPE strings were provided in the input data. Affected versions confirmed via EUVD: Android 14, 15, 16, 16-QPR2, and 17.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local attack via installed app (AV:L), low privilege required (PR:L), no user interaction, scope unchanged, full device impact on successful escalation.
Primary rating from Vendor (android).
CVSS VectorVendor: android
Lifecycle Timeline
3DescriptionCVE.org
In onCreate of SlicePermissionActivity.java, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Executive ViewAI
CVE-2026-28614 is a privilege escalation vulnerability in Android 14-17 that allows an installed application to gain full administrative control over device functions, data, and communications. Organizations with Android device deployments or BYOD programs face risk from this attack vector: any low-privilege app a user installs could silently escalate to complete device control without additional user interaction.
Enable and enforce Google Play Protect on all Android 14-17 devices; restrict application installation to the official Google Play Store and disable sideloading; deploy mobile device management (MDM) to monitor and restrict suspicious applications; enable continuous threat detection for anomalous privilege escalation patterns; monitor Google's Android Security & Privacy bulletin for patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-73964
GHSA-c6jr-fjv5-8xfv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB