Read the docs
TI-2026-80444 Aliases CVE-2026-112345GHSA-cr86-mm6w-6p6g

Hardcoded AES key in TTLock app exposes BLE pairing keys

Priority HIGH 72CWE-321Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-321.

Summary

TTLock Android application before 9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key, tracked as CWE-321. An attacker within Bluetooth range can decrypt the per-pairing session key sent during BLE pairing, using the embedded defaultKey. The attacker can then forge authenticated BLE requests to unlock the device, add fingerprints or access codes, and perform administrative actions without authentication or user interaction. A public proof of concept is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00245 15th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed TTLock (Sciener): 9.8.260718

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ScienerTTLockbefore 9.8.2607189.8.260718Patch availableCNA
  • TTLock VendorSciener Affected before 9.8.260718 Fixed in 9.8.260718 Patch available CNA

Remediation

Update the TTLock Android application from Sciener to version 9.8.260718 or later, which is the fixed version listed for this product.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA TTLock (Sciener) Fixed in 9.8.260718

Timeline

  1. 2026-10-26 Threatist record created from CVE-2026-112345
  2. 2026-10-26 CISA SSVC decision points changed
  3. 2026-10-26 Priority changed: MEDIUM → HIGH
  4. 2026-10-27 Alias added: GHSA-cr86-mm6w-6p6g

References

Exploit 1

  • TI-2023-06403 The unlockKey character in a lock using Sciener firmware can be brute forced through… CVSS 3.1CRITICAL 9.1
  • TI-2023-06406 Some Sciener-based locks support plaintext message processing over Bluetooth Low Energy… CVSS 3.1HIGH 8.2
  • TI-2023-06400 The AES key utilized in the pairing process between a lock using Sciener firmware and a… CVSS 3.1MEDIUM 6.8
  • TI-2023-06401 Improper verification of communication channel in Sciener TTLock App CVSS 3.1MEDIUM 6.5
  • TI-2023-06414 Sciener locks' firmware update mechanism do not authenticate or validate firmware updates… CVSS 3.1CRITICAL 9.8
  • TI-2023-06402 A specially crafted message can be sent to the TTLock App that downgrades the encryption… CVSS 3.1HIGH 7.5
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences