Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 26 Oct 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-26T16:15:26.221Z
Reserved: 2026-10-19T14:41:46.702Z
Link: CVE-2026-112345
No data.
Status : Received
Published: 2026-10-26T15:16:38.167
Modified: 2026-10-26T15:16:38.167
Link: CVE-2026-112345
No data.
OpenCVE Enrichment
Updated: 2026-10-26T16:30:11Z
-
CWE-321
Use of Hard-coded Cryptographic Key