CVE-2026-9220: Shenzhen i365-Tech Setracker2 Parental Control App (Android) package com.tgelec.setracker · Use of Hard-coded Cryptographic Key
Affects Shenzhen i365-Tech Setracker2 Parental Control App (Android) package com.tgelec.setrackerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Shenzhen i365-Tech Co. Ltd.Setracker2 Parental Control App (Android) package com.tgelec.setracker | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider limiting use of affected versions and monitor for vendor updates. No official or temporary fixes are currently documented.
Description
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.