Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall low-privileged malicious app
-
DeliveryCraft deceptive app label string
-
ExploitInvoke ForgetDeviceDialogFragment with spoofed context
-
ExecutionUser taps confirm on misleading dialog
-
PersistTrusted companion device unpaired
-
ImpactAttacker gains elevated privileges via removed trust binding
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security UI security representation
|
| Exploitation Conditions | Attacker must already have local code execution on the device as a low-privileged installed app (CVSS PR:L, AV:L) on Android 16 or Android 16-qpr2, and must be able to invoke or influence the Settings ForgetDeviceDialogFragment flow with an attacker-controlled application label. The user must reach and dismiss the misleading dialog for the privilege change to materialize; the CVE marks UI:N because no additional interaction beyond the standard dialog is required of the attacker's app, but the deception itself relies on the user tapping confirm. Limiting factors: requires a malicious app already installed, requires the target to have a forgettable companion device whose removal yields a privilege benefit, and is constrained to the affected Android 16 branches. |
| Impact | Signals are mixed and should be read carefully. CVSS 7.8 with AV:L/AC:L/PR:L/UI:N/C:H/I:H/A:H reflects the worst-case 'total' technical impact CISA SSVC also assigns, but the same SSVC record marks Exploitation as 'none' and Automatable as 'no', so this is not a mass-exploit candidate. There is a contradiction worth flagging: the CVE description says 'User interaction is not needed for exploitation' yet the vulnerability is fundamentally a UI deception that requires a human to tap 'Forget' on a misleading dialog - the UI:N likely refers to the attacking app not needing extra user interaction beyond the routine dialog the user already expects, not to fully silent exploitation. No EPSS score, no KEV listing, and no public PoC are reported. Realistic priority: moderate; worth patching in the normal Android monthly cycle but not an emergency. |
| Exploit ScenarioDerived | A user installs a low-privileged malicious app (for example, a free utility from a third-party store). The app crafts an application label that mimics a trusted companion-device manager and triggers the ForgetDeviceDialogFragment so the user, believing they are confirming a benign action, taps through and unpairs a security-relevant companion device such as a smartwatch trust agent or an enterprise-managed peripheral, removing the trust binding the attacker wants gone. No public PoC is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 02, 2026
Local privilege escalation in Android 16 and Android 16-qpr2 allows a low-privileged app to deceive the user into forgetting a paired Bluetooth or companion device via a misleading UI in the ForgetDeviceDialogFragment. No public exploit identified at time of analysis, and CISA SSVC marks exploitation status as 'none' with total technical impact. The flaw is a UI spoofing weakness (CWE-451) reachable without any user interaction beyond normal dialog acknowledgement.
RemediationAI
Apply the June 2026 Android security patch level (2026-06-01 or later) from the Android Security Bulletin at https://source.android.com/docs/security/bulletin/2026/2026-06-01; OEM and carrier rollouts based on this bulletin are the authoritative fix. Patch available per vendor advisory; an exact AOSP tag is not enumerated in the supplied data, so confirm the build fingerprint after update. Until devices receive the patch, compensating controls are limited because the dialog is in system UI: restrict installation to vetted apps from Play (Play Protect plus Advanced Protection where available), discourage sideloading on managed fleets via MDM, and train users to verify the device name shown on a 'Forget device' prompt against the Bluetooth/Companion settings list before confirming - the trade-off is added friction for legitimate unpair flows.
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 defect lives in the getAppLabel routine of ForgetDeviceDialogFragment.java, a Settings/SystemUI component that renders the 'Forget device' confirmation dialog for paired companion devices. The CWE-451 (User Interface Misrepresentation of Critical Information) classification indicates that the label returned for the calling app is insufficiently validated or sanitized, so a malicious app can supply a deceptive application name or context string that causes the dialog to misrepresent which device or which requesting app is involved. Because the dialog is part of trusted system UI but pulls untrusted attacker-controlled strings, the user is tricked into authorizing an action against a different device than they believe. The CPE cpe:2.3:a:google:android scope confirms this is in the Android platform/AOSP layer rather than a third-party OEM addition.
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:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (google_android) · only source for this CVE.
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In getAppLabel of ForgetDeviceDialogFragment.java, there is a possible trick the user into forgetting a device due to misleading or insufficient UI. 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-0096 affects Android 16 and 16-qpr2, enabling low-privileged applications to manipulate user trust relationships by spoofing Bluetooth device pairing interfaces. This privilege escalation could allow third-party apps to isolate users from critical connected devices, creating security and operational continuity risks. No patch is currently available, requiring immediate interim controls.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict app installation to managed marketplaces via device policy; limit Bluetooth permissions to essential, pre-approved applications only; deploy mobile device management (MDM) to monitor privilege grants and detect suspicious app activity; educate users to report unexpected disconnections from trusted Bluetooth devices; monitor system logs for unauthorized device pairing modifications; disable Bluetooth when not actively required.
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-33806
GHSA-7p95-c5qm-8mrx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB