Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker distributes malicious Android app
-
DeliveryVictim installs app on Android 14-17 device
-
ExploitVictim navigates to Manage Space in device Settings
-
ExecutionMalicious app intercepts unsafe PendingIntent from StorageManagerService
-
PersistRedirects activity launch to privileged system component
-
ImpactAchieves full C/I/A compromise on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Improper export of Android components
|
| Exploitation Conditions | Requires a malicious application to be installed on the target device with at least user-level (low privilege) execution - this is the primary gatekeeping condition. User interaction is required: the victim must actively navigate to the Manage Space flow for an application in the device Settings, causing StorageManagerService to generate and dispatch the vulnerable PendingIntent. Exploitation is strictly local (AV:L); network-based or zero-click remote exploitation is not possible for this vulnerability. The SSVC assessment confirms the attack is not automatable. Limiting factors include: the requirement for the victim to take a specific UI action, the need for a malicious app to already be present on the device, and restriction to Android 14-17 (earlier versions are not listed in the advisory). |
| Impact | The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) accurately reflects the attack profile: exploitation requires an installed malicious app, user-triggered navigation into storage management, and physical device access, all of which constrain real-world exploitability. The EPSS score of 0.12% (2nd percentile) and SSVC exploitation status of 'none' are internally consistent and indicate no current active exploitation. Despite the SSVC rating of 'Technical Impact: total,' the non-automatable nature of the attack (requires user interaction, cannot be chained remotely) meaningfully reduces urgency - even a mid-sized municipal IT team in legnica managing a mixed Android BYOD fleet should treat this as a standard patch-cycle priority rather than an emergency, absent evidence of targeted in-the-wild use. The breadth of affected versions (Android 14-17) across billions of devices does, however, make this a high-aggregate-risk finding even at low individual-exploitation probability. |
| Exploit ScenarioDerived | An attacker distributes a trojanized Android application - disguised as a utility or game - that a victim installs on their Android 14-17 device; when the victim subsequently opens the system storage management interface (for example, via Settings → Apps → select any app → Manage Space), StorageManagerService generates the vulnerable PendingIntent and delivers it in a way the malicious app can intercept. The attacker's app modifies the intent to redirect the activity launch to a privileged system component, gaining full access to device data, credentials, and settings without requiring any additional permissions beyond those already held by the malicious app. |
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 StorageManagerService (Android 14 through 17) stems from an unsafe PendingIntent in getManageSpaceActivityIntent that enables a LaunchAnyWhere attack chain, allowing a malicious low-privilege app to intercept and redirect activity launches into privileged system contexts. The vulnerability requires user interaction - specifically navigating the storage management UI - but once triggered, yields full compromise of confidentiality, integrity, and availability on the device. No public exploit has been identified at time of analysis; Google's September 2026 Android Security Bulletin documents the fix.
RemediationAI
Apply all security patches at or above the 2026-09-01 Android security patch level as described in the Android Security Bulletin at https://source.android.com/docs/security/bulletin/2026/2026-09-01. The exact patched build version is not independently confirmed in the available references beyond the patch-level date. OEMs and carriers must integrate these patches into device-specific builds and distribute them over-the-air; end users should apply system updates promptly once their device vendor makes them available. For enterprise Android fleets managed via MDM, enforce a minimum security patch level policy of 2026-09-01 and quarantine non-compliant devices from corporate resources. As a compensating control prior to patch availability, restrict installation of apps from unknown sources and limit device exposure to untrusted applications, which removes the prerequisite malicious app required for exploitation; note this control may not prevent pre-installed malware.
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
The vulnerability resides in StorageManagerService.java within the Android framework, where getManageSpaceActivityIntent constructs a PendingIntent that is either mutable or implicit, making it susceptible to interception or modification by an untrusted application. CWE-926 (Improper Export of Android Application Components) describes this root cause: when a PendingIntent lacks strict targeting or mutability restrictions, a malicious recipient application can alter the enclosed intent - changing its component, action, or extras - before it is consumed by a privileged caller. This enables the well-documented LaunchAnyWhere technique, where an attacker uses the hijacked PendingIntent to start arbitrary Activity components not normally accessible from their privilege level, effectively inheriting the caller's permissions. The EUVD advisory EUVD-2026-74003 confirms the flaw spans 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:R/S:U/C:H/I:H/A:H
Local attack via installed malicious app (AV:L, PR:L); victim must trigger storage management UI (UI:R); successful exploit yields full device compromise with no scope change (C:H/I:H/A:H, S:U).
Primary rating from Vendor (android).
CVSS VectorVendor: android
Lifecycle Timeline
3DescriptionCVE.org
In getManageSpaceActivityIntent of StorageManagerService.java, there is a possible LaunchAnyWhere chain due to an unsafe PendingIntent. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Executive ViewAI
Local privilege escalation in Android 14-17 StorageManagerService enables a malicious low-privilege app to achieve full device compromise-access to all data, ability to modify or delete information, and denial of service-when a user navigates the storage management interface. Organizations managing Android devices (company-issued or BYOD) face potential breach of credentials, customer data, and communications stored on affected devices.
Monitor Google's September 2026 Android Security Bulletin for security update availability and deploy OTA or MDM-delivered patches when released. Pending patching, enforce MDM-based controls: restrict unknown app sources, deny broad app permission grants (storage, file system, phone state), block storage management UI access where organizational workflow permits, and disable installation from untrusted app stores.
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-74003
GHSA-3wf6-jr8m-5hxq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB