Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious low-privilege app
-
ExploitInvoke device-admin preference code path
-
ExecutionTrigger logic-error permission bypass
-
ImpactGain escalated privileges locally
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a local foothold: an attacker-controlled app already installed and running on the affected device (Android 14, 15, or 16-qpr2), consistent with AV:L/PR:L. The flaw is a logic error in DeviceAdminAppsPreferenceController.updateState that bypasses a permission check within the device-admin apps preference flow, so the attacker must be able to reach that Settings code path. Limiting factors that reduce real-world risk: no remote network vector (must have code execution on-device first), and per CISA SSVC the flaw is not automatable (cannot be reliably mass-exploited). Mitigating that risk slightly is that no user interaction is required (UI:N), so once the malicious app is present it can act silently. |
| Impact | This is a credible but not emergency-tier issue. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local privilege escalation requiring an already-present low-privileged context (a malicious or compromised app) on the device - not a remotely reachable flaw. CISA SSVC reinforces a measured priority: Exploitation=none (no observed or public exploitation), Automatable=no (cannot be reliably mass-exploited/wormed), but Technical Impact=total (full compromise of the component's confidentiality, integrity, and availability once triggered). There is no CISA KEV listing and no POC indicator in the provided data, and no EPSS score was supplied, so exploitation probability cannot be quantified from this input. All signals are internally consistent: a logic error producing a permission bypass is exactly the kind of local EoP that scores high on impact yet depends on a foothold and is hard to automate at scale. Net: treat as a standard high-severity Android monthly-bulletin patch - important for devices processing untrusted apps, but not evidence of active, widespread attack. No conflicting signals were detected in the data. |
| Exploit ScenarioDerived | A user installs a malicious or compromised low-privilege app on an affected Android/AAOS device. The app abuses the logic error in DeviceAdminAppsPreferenceController.updateState to bypass a permission check, gaining elevated privileges without any user interaction or additional execution rights. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
A permission bypass logic error in Android's DeviceAdminAppsPreferenceController.updateState allows a locally installed, running app to escalate privileges, granting it high confidentiality and integrity impact on affected devices (Android 14, 15, and 16-qpr2). Exploitation requires a local foothold consistent with the assessed CVSS vector (AV:L/PR:L) - the attacker must already have a malicious app executing on the device and be able to reach the device-admin apps preference code path - but no user interaction is needed, so the escalation can occur silently once that app is present. There is no remote attack vector, CISA SSVC records exploitation as 'none' and the flaw as non-automatable (cannot be reliably mass-exploited), and no public exploit code has been identified at time of analysis. This is a credible but not emergency-tier issue.
RemediationAI
Apply the vendor fix from the Android security bulletin dated 2026-10-01 (https://source.android.com/docs/security/bulletin/aaos/2026/2026-10-01) - patch availability is confirmed per vendor advisory, and the bulletin should be consulted for the exact patched build identifiers applicable to Android 14, 15, and 16-qpr2; there is no exact fix version stated in the provided data, so do not assume a version number. Update through the normal OEM/AAOS over-the-air channel and verify the device security patch level reflects the October 2026 bulletin; note that OEM and carrier staging can delay availability, so track patch-level compliance per device fleet. Where patching cannot be applied immediately, compensating controls that reduce the required local foothold are the most effective: enforce Google Play Protect and restrict installation to trusted sources via MDM (side-loading must be blocked, which also prevents enterprise-approved internal distribution of unsigned APKs); require managed devices to run only allow-listed applications; and monitor for apps that request or receive device-administrator privileges unexpectedly. These controls reduce risk only against an attacker who has not yet obtained code execution - an already-installed malicious app that reaches the Settings device-admin preference path can still trigger the bypass, and none of these controls address the logic error itself. Given the local-only vector and SSVC's 'not automatable' determination, mass exploitation pressure is low, but privilege-escalation chains on Android frequently pair a local EoP like this with a separate initial-access bug.
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 flaw is a logic error (CWE-269, Improper Privilege Management) in DeviceAdminAppsPreferenceController.java, part of the Settings application's handling of device-administrator app preferences. The updateState method is intended to reflect and enforce the state of device-admin apps in the Settings UI/backing store; a mistake in that logic allows the permission check protecting this flow to be bypassed. Because the affected component governs which applications may hold or appear as device administrators - a highly privileged role that can enforce policies, lock devices, and interact with managed configuration - bypassing the check yields local elevation of privilege with high impact to confidentiality and integrity (C:H/I:H) and no special execution privileges required beyond running a local app. The root cause class is authorization/business-logic failure rather than memory corruption, so no memory-safety mitigations (ASLR, sandbox hardening against memory bugs) would prevent it. Affected per the CPE data is the Google Android platform (cpe:2.3:a:google:android) across Android 14, Android 15, and Android 16-qpr2.
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 app foothold required (AV:L, PR:L); no user interaction (UI:N); logic bug reliably triggered (AC:L); full privilege gain yields total impact (C/I/A:H), no scope change (S:U).
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In updateState of DeviceAdminAppsPreferenceController.java, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Executive ViewAI
A privilege-escalation logic flaw in Android 14, 15, and 16-qpr2 device-admin preference handling (CVE-2026-28647) allows an already-installed malicious app to silently gain elevated access to sensitive data and system settings on affected devices. Because no vendor patch is currently available, every Android handset and tablet in our managed fleet on these versions remains exposed until Google ships a fix. Leadership should care because this affects the mobile devices used for corporate email, MFA, and access to internal systems, and the flaw can be triggered without any user prompting once a bad app is present - though exploitation requires local app installation and is not remotely reachable or mass-exploitable, keeping this a manageable rather than crisis-level risk.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce MDM policy blocking sideloading and installation from unknown sources; restrict Device Administrator and Device Owner provisioning to a vetted app allowlist and remove unnecessary grants; require Google Play Protect / mobile threat defense scanning and alerting on device-admin state changes; isolate corporate data in a managed work profile with container controls; and prioritize devices with developer options enabled for monitoring and user re-education. Note the flaw cannot be triggered remotely and requires an authenticated local app already running on the device, and no public exploit code exists at time of analysis.
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-92629
GHSA-fv7f-jc64-wr7h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB