High · CVSS 8.6CVE-2026-112345

TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key ExposureCVE-2026-112345

Answer in brief

CVE-2026-112345 records a High severity (CVSS 8.6) vulnerability in TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure. The current sources do not mark it as known exploited. The current feed maps Sciener/TTLock (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 26, 2026Updated Oct 26, 2026Source checked Oct 26, 2026First seen by HOL Oct 26, 2026Material review Oct 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Sciener/TTLock (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Sciener/TTLockgeneric	>=0 <9.8.260718	9.8.260718

Recommended response

Check inventory. Check lockfiles and deployed manifests for Sciener/TTLock.
Review the reported fix. Update Sciener/TTLock to 9.8.260718 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.