Skip to main content
VulnerabilityPublished Updated

CVE-2026-9221: Shenzhen i365-Tech Setracker2 Parental Control App (Android) package com.tgelec.setracker · Weak Cryptography

Affects Shenzhen i365-Tech Setracker2 Parental Control App (Android) package com.tgelec.setrackerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Shenzhen i365-Tech Co. Ltd.Setracker2 Parental Control App (Android) package com.tgelec.setrackerAffected
  • <=3.1.5
Fixed in–

AI-suggested

Until an official fix is available, users and administrators should be cautious about using versions 3.1.5 and earlier. Monitoring vendor communications for updates or patches is recommended.

Description

The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.1.5 and earlier uses MD5 to generate a request signature for authenticating communications between the mobile client and the backend REST API. Attackers could potentially reverse the signature to recover the session ID. With the session ID exposed, an attacker could impersonate the legitimate user and issue authenticated API requests.

References

Community reviews

Loading reviews…