CVE-2026-112345: TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure
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.
Affected Software
Event History
Frequently Asked Questions
How can I identify affected Android app installations?
TTLock Android app versions earlier than 9.8.260718 are affected. The provided information does not identify specific affected firmware versions for associated smart locks.
What access does an attacker need to exploit this issue?
The attacker must be within Bluetooth range and able to observe a BLE pairing exchange. No prior authentication or user interaction is required.
What could an attacker do after recovering the session key?
An attacker can forge authenticated BLE requests to unlock the device, add fingerprints or access codes, and perform administrative actions.