---
id: CVE-2026-112345
title: TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure
summary: >-
  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 BL…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'
cvssSource: cna
cwe:
  - CWE-321
vendor: Sciener
product: TTLock
affected:
  - TTLock < 9.8.260718
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-26T16:06:18.962111Z'
exploitAvailable: true
published: '2026-10-26'
updated: '2026-10-26'
sourceUpdated: '2026-10-26T17:16:05.283Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-112345'
references:
  - url: 'https://damiri.fr/en/cve/CVE-2026-112345'
    label: Researcher Disclosure
  - url: >-
      https://www.vulncheck.com/advisories/ttlock-android-app-hardcoded-ble-pairing-key-exposure
    label: >-
      VulnCheck Advisory: TTLock Android App < 9.8.260718 Hardcoded BLE Pairing
      Key Exposure
tags:
  - cve.org
  - exploit-available
ingestedAt: '2026-10-26T15:29:30.516Z'
---

## Overview

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

- `TTLock < 9.8.260718`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.