CVE-2026-112345
Received Received - Intake

Hardcoded AES Key in TTLock Android App and Firmware

Publication date: 2026-10-26

Last updated on: 2026-10-26

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-26
Last Modified
2026-10-26
Generated
2026-10-26
AI Q&A
2026-10-26
EPSS Evaluated
N/A
NVD
CVE-2026-112345
EUVD
EUVD-2026-109945

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Sciener TTLock 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-321 The product uses a hard-coded, unchangeable cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a hardcoded static AES key in the TTLock Android app before version 9.8.260718 and its smart-lock firmware. An attacker within Bluetooth range can decrypt the session key exchanged during BLE pairing using this embedded key. This allows them to forge authenticated requests to unlock devices, add fingerprints or access codes, and perform admin actions without authentication.

Detection Guidance

Detecting this vulnerability requires checking for outdated TTLock Android app versions (before v9.8.260718) and inspecting BLE communication for hardcoded AES key usage. Monitor network traffic for unauthorized BLE commands or device interactions. Use Bluetooth sniffing tools like Wireshark with BLE plugins to analyze pairing exchanges.

Impact Analysis

If you use a vulnerable TTLock device, an attacker nearby could unlock it, add unauthorized fingerprints or access codes, and perform admin actions without your knowledge. This bypasses authentication and requires no user interaction.

Mitigation Strategies

Immediately update the TTLock Android app to version 9.8.260718 or later. Disable Bluetooth access to TTLock devices if not in use. Implement network segmentation to isolate smart-lock systems. Monitor for suspicious BLE activity or unauthorized device access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-112345. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart