Shenzhen i365-Tech Setracker2 Parental Control App package com.tgelec.setracker generation of predictable numbers or identifiers
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.28- |
Summary
A vulnerability marked as critical has been reported in Shenzhen i365-Tech Setracker2 Parental Control App package com.tgelec.setracker up to 3.1.5. This vulnerability affects unknown code. Performing a manipulation results in generation of predictable numbers or identifiers. This vulnerability is identified as CVE-2026-9219. The attack can be initiated remotely. There is not any exploit available.
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 classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a generation of predictable numbers or identifiers vulnerability. CWE is classifying the issue as CWE-340. The product uses a scheme that generates numbers or identifiers that are more predictable than required. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior have a predictable registration ID derived from IMEI. The enrollment system lacks additional authentication before assignment. If an attacker is able to obtain the registration ID, they would be able to arbitrarily enroll watches belonging to other users.
The weakness was released by Huancheng Hu. It is possible to read the advisory at raw.githubusercontent.com. This vulnerability is uniquely identified as CVE-2026-9219 since 05/21/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/26/2026). The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
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
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.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.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: Generation of predictable numbers or identifiersCWE: CWE-340 / CWE-331 / CWE-330
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-9219 (🔒)
GCVE (CVE): GCVE-0-2026-9219
GCVE (VulDB): GCVE-100-374091
Entry
Created: 06/26/2026 07:37Changes: 06/26/2026 07:37 (73)
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.