Session-ID disclosure via reversible MD5 request signatures
Published Jun 25, 2026 · Updated Jun 25, 2026
Cryptographic weakness in SeTracker2 3.1.5 and earlier allows remote attackers to recover session IDs from MD5 request signatures. The Android client uses MD5 to generate REST API request signatures, allowing recovery of the session identifier carried by the signature scheme. No credentials or user interaction are required; recovered identifiers permit account impersonation and authenticated API requests, with no reported integrity or availability impact.
Summary
What happened
Cryptographic weakness in SeTracker2 3.1.5 and earlier allows remote attackers to recover session IDs from MD5 request signatures. The Android client uses MD5 to generate REST API request signatures, allowing recovery of the session identifier carried by the signature scheme. No credentials or user interaction are required; recovered identifiers permit account impersonation and authenticated API requests, with no reported integrity or availability impact.
The record
- CVE
- CVE-2026-9221
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Shenzhen i365-Tech Co., Ltd.
- Product
- SeTracker2
- Classifications
- CWE-327, T1635
- 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?
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.
Weakness, pattern, technique
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