Google Android up to 17 ClipboardService ClipboardService.java setClipboardAccessNotificationsEnabledForUser isolation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in Google Android 14/15/16/16-qpr2/17. The affected element is the function setClipboardAccessNotificationsEnabledForUser of the file ClipboardService.java of the component ClipboardService. This manipulation causes isolation.
The identification of this vulnerability is CVE-2026-28602. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability was found in Google Android 14/15/16/16-qpr2/17. It has been declared as problematic. Affected by this vulnerability is the function setClipboardAccessNotificationsEnabledForUser of the file ClipboardService.java of the component ClipboardService. The manipulation with an unknown input leads to a isolation vulnerability. The CWE definition for the vulnerability is CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In setClipboardAccessNotificationsEnabledForUser of ClipboardService.java, there is a possible mult-iuser isolation 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.
It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2026-28602 since 03/02/2026. The exploitation appears to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/08/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: IsolationCWE: CWE-653
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/02/2026 CVE reserved09/08/2026 Advisory disclosed
09/08/2026 VulDB entry created
09/08/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2026-28602 (🔒)
GCVE (CVE): GCVE-0-2026-28602
GCVE (VulDB): GCVE-100-400219
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 09/08/2026 21:05Changes: 09/08/2026 21:05 (56)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.