Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local device access or install malicious app
-
DeliveryInvoke DisableSupervisionActivity directly
-
ExploitTrigger missing null check in onCreate()
-
ExecutionSupervision enrollment data deleted
-
PersistMDM/enterprise policy controls removed
-
ImpactOperate device with escalated capabilities outside organizational oversight
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 local access to the target device - either physical access or an installed application running on an Android 16-QPR2 device, consistent with the CVSS local attack vector (AV:L). Within that local context, no additional execution privileges are required (PR:N per CVSS) and no user interaction is needed (UI:N per CVSS). The critical limiting condition is that the target device must be actively enrolled in an Android supervision or MDM program that provisions DisableSupervisionActivity - on unmanaged consumer devices, the supervision data that is deleted does not exist, substantially limiting meaningful impact. Exploitation is confirmed only against Android 16-QPR2; other Android versions are not confirmed affected. The attack is further limited to scenarios where a malicious actor can install or run an application locally, or has direct physical access - remote unauthenticated exploitation is not possible given the local attack vector. |
| Impact | The CVSS 6.8 score with vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N presents a nuanced risk profile. The local attack vector (AV:L) materially constrains the attack surface relative to network-exploitable flaws, but the combination of no required privileges (PR:N), no user interaction (UI:N), and low complexity (AC:L) means any app or user with device access can trivially trigger the condition. The high confidentiality impact (C:H) reflects access to supervision-controlled data, while low integrity impact (I:L) reflects the deletion or modification of supervision records. EPSS at 0.01% (1st percentile) confirms extremely low observed exploitation probability, and the vulnerability does not appear in CISA KEV. The real-world risk is concentrated in enterprise and education deployments using Android MDM supervision - for those environments, the privilege escalation impact is significant because removing supervision data bypasses the organizational security boundary. For unmanaged consumer devices, practical impact is minimal as no supervision data exists to be targeted. No conflicting signals were identified between CVSS and description; the local vector is consistent with the described attack path. |
| Exploit ScenarioDerived | An unprivileged malicious application installed on an enterprise-managed Android 16-QPR2 device directly invokes DisableSupervisionActivity, triggering the missing null check in onCreate() and causing the supervision enrollment data to be deleted. With MDM supervision controls removed, the app or user gains access to device capabilities and data that were previously restricted by organizational policy - such as unenforced app restrictions, bypassed screen-time controls, or disabled remote wipe policies. No public exploit identified at time of analysis, but the low complexity (AC:L) indicates the mechanism would be straightforward to reproduce given source access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 02, 2026
Local privilege escalation in Google Android 16-QPR2 enables an unprivileged local actor to delete device supervision data by exploiting a missing null check in the onCreate() method of DisableSupervisionActivity.kt, effectively dismantling enterprise MDM controls without requiring elevated privileges or user interaction. The flaw (CWE-269: Improper Privilege Management) is bounded to local access but operates with no authentication prerequisite, making it exploitable by any installed app or local user on a supervised managed device. No public exploit identified at time of analysis, and an EPSS of 0.01% reflects negligible observed exploitation probability; however, organizational risk in enterprise Android deployments is disproportionately higher than the base score suggests.
RemediationAI
Apply the security update documented in Google's Android Security Bulletin for June 1, 2026, available at https://source.android.com/docs/security/bulletin/2026/2026-06-01; the exact patched build number should be verified directly from that bulletin, as no specific patched release version is independently confirmed in the available data. OEM device manufacturers typically distribute these patches through standard over-the-air update channels, so enterprise administrators should verify which OEM builds incorporate the June 2026 SPL (Security Patch Level). For enterprise environments where immediate patching is delayed, administrators should evaluate restricting invocation of DisableSupervisionActivity via MDM policy configuration - note this trade-off may interfere with legitimate supervision lifecycle management workflows. Limiting physical and logical device access to trusted personnel reduces exposure in the interim. No workaround is confirmed in the provided data beyond the vendor patch.
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 DisableSupervisionActivity.kt, a component of Android's enterprise device supervision framework, within the Activity lifecycle callback onCreate(). A missing null check on an expected input or object reference allows an attacker to trigger the supervision data deletion path without proper validation or privilege enforcement. CWE-269 (Improper Privilege Management) identifies the root cause as a failure to enforce appropriate privilege boundaries during a sensitive operation - supervision data deletion - which should be guarded against unprivileged invocation. Android device supervision is the mechanism used by MDM (Mobile Device Management) solutions and parental controls to enforce organizational policies on enrolled devices. The CPE string cpe:2.3:a:google:android:*:*:*:*:*:*:*:* covers the Android application platform layer, with ENISA EUVD-2026-33798 narrowing the confirmed affected surface to Android 16-QPR2 specifically.
Know when the next one hits your stack
- 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:N/UI:N/S:U/C:H/I:L/A:N
Primary rating from Vendor (google_android) · only source for this CVE.
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In onCreate of DisableSupervisionActivity.kt, there is a possible way to delete supervision data due to a missing null check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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.
EUVD-2026-33798
GHSA-vgqp-c67c-r79g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB