Shenzhen i365-Tech Setracker2 Parental Control App package com.tgelec.setracker hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 1.87 |
Summary
A vulnerability described as problematic has been identified in Shenzhen i365-Tech Setracker2 Parental Control App package com.tgelec.setracker up to 3.1.5. This issue affects some unknown processing. Executing a manipulation can lead to hard-coded key. This vulnerability is tracked as CVE-2026-9220. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in Shenzhen i365-Tech Setracker2 Parental Control App package com.tgelec.setracker up to 3.1.5. It has been declared as problematic. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a hard-coded key vulnerability. The CWE definition for the vulnerability is CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. As an impact it is known to affect confidentiality. CVE summarizes:
Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior encrypts requests between the watch and its backend with static hardcoded AES keys and initialization vectors. This allows an attacker to decrypt Setracker2 watch traffic.
The weakness was disclosed by Huancheng Hu. The advisory is shared for download at raw.githubusercontent.com. This vulnerability was named CVE-2026-9220 since 05/21/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (icscert): 🔒
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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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
05/21/2026 CVE reserved06/26/2026 Advisory disclosed
06/26/2026 VulDB entry created
06/26/2026 VulDB entry last update
Sources
Advisory: raw.githubusercontent.comResearcher: Huancheng Hu
Status: Not defined
CVE: CVE-2026-9220 (🔒)
GCVE (CVE): GCVE-0-2026-9220
GCVE (VulDB): GCVE-100-374092
Entry
Created: 06/26/2026 07:37Changes: 06/26/2026 07:37 (73)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.