CVE-2026-112345
TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure
- State
- Published
- Severity
- 8.6 High
- Published
- Oct 26, 2026
- Updated
- Oct 27, 2026
- Reserved
- Oct 19, 2026
Description
TTLock Android application before v9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key vulnerability that allows an attacker within Bluetooth range to decrypt the per-pairing session key transmitted during BLE pairing. Attackers can observe the pairing exchange, recover the persistent session key using the embedded defaultKey, and forge authenticated BLE requests to unlock the device, add fingerprints or access codes, and perform administrative actions without authentication or user interaction.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 8.6 High | CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | VulnCheck |
| 3.1 | 8.1 High | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | VulnCheck |
Weaknesses
- CWE-321 Use of Hard-coded Cryptographic Key
Affected Products
| Product | Versions |
|---|---|
TTLockSciener |
|
References
- Researcher Disclosuretechnical-descriptionexploit
- VulnCheck Advisory: TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposurethird-party-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.