Watch traffic disclosure via static AES secrets
Published Jun 25, 2026 · Updated Jun 25, 2026
Hard-coded cryptographic keys in SeTracker2 3.1.5 and earlier allow remote attackers to decrypt traffic between watches and the backend. The Android app encrypts requests with static AES keys and initialization vectors embedded in the client, making the same secrets recoverable and reusable across installations. Exploitation requires access to encrypted watch traffic; the reported impact is disclosure of its contents, not modification or service interruption.
Summary
What happened
Hard-coded cryptographic keys in SeTracker2 3.1.5 and earlier allow remote attackers to decrypt traffic between watches and the backend. The Android app encrypts requests with static AES keys and initialization vectors embedded in the client, making the same secrets recoverable and reusable across installations. Exploitation requires access to encrypted watch traffic; the reported impact is disclosure of its contents, not modification or service interruption.
The record
- CVE
- CVE-2026-9220
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Shenzhen i365-Tech Co., Ltd.
- Product
- SeTracker2
- Classifications
- CWE-321, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo