TTLock: Hardcoded AES key in Android app and smart-lock firmware (CVE-2026-112345)
TTLock Android applications before v9.8.260718 and associated smart-lock firmware utilize a hardcoded static AES key, allowing an attacker within Bluetooth range to intercept session keys and forge administrative commands.
CVE search metadata
CVE search record: CVE-2026-112345. Severity: high. CVSS: 8.1. KEV: no. Product: TTLock Android application (< 9.8.260718), smart-lock firmware. Brief: TTLock: Hardcoded AES key in Android app and smart-lock firmware (CVE-2026-112345). Brief link: https://feed.craftedsignal.io/briefs/2026-10-ttlock-ble-vulnerability/
Triage facts
Revision 1- Applicability
- TTLock Android application (< 9.8.260718), smart-lock firmware
- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 1Oct 26, 19:44 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A2Roughly even chance
TTLock Android application versions prior to v9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key. This vulnerability allows an attacker within Bluetooth range to decrypt the per-pairing session key, recover the persistent session key, and forge authenticated BLE requests to unlock the device, add fingerprints or access codes, or perform administrative actions without authentication or user interaction.