CVE-2026-9220
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk14th percentile - higher than 14% of all known CVEs
Summary
The Setracker2 Android Companion App versions 3.1.5 and prior encrypts communication between the watch and its backend using static hardcoded AES keys and initialization vectors. This allows an attacker to decrypt Setracker2 watch traffic.
Risk Assessment
Decrypting the traffic may lead to exposure of sensitive data transmitted between the device and the server, such as location or personal user information.
Recommendation
Immediately update the Setracker2 app to the latest available version that fixes this vulnerability, and avoid using versions 3.1.5 and older.
Other vulnerabilities in Setracker2 Android Companion App (com.tgelec.setracker) wersje 3.1.5 i starsze
See all- CVE-2026-9222High
The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.1.5 and prior only require the password hash when authenticating with backend services from the client. An attacker who knows the hash can authenticate and gain full access.
- CVE-2026-9219Medium
The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.1.5 and prior generate a predictable registration ID derived from IMEI. The enrollment system lacks additional authentication before assignment, allowing an attacker who obtains the registration ID to arbitrarily enroll watches belonging to other users.
Original NVD description (English source)
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.