Live › vulnerability › CVE-2026-112345
Go to dashboardThe TTLock Android app and its smart-lock firmware ship a hardcoded static AES key used to protect the per-pairing session key sent over Bluetooth Low Energy. A nearby attacker can record a pairing exchange, decrypt the session key with the embedded key, and forge requests to unlock the lock or add access codes.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 16:02 UTC. All times on this page are UTC.
Anyone who uses the TTLock Android app to pair and manage Bluetooth smart locks, and the locks themselves, since the flaw is in both the app and the firmware. The sources do not say whether iOS builds or locks managed by other apps are affected. Teams that never used TTLock hardware can skip it.
No product ranges from the sources yet.
9.8.2607189.8.260718 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-112345")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.