# CVE-2026-112345: TTLock Android App < 9.8.260718 Hardcoded BLE Pairing Key Exposure


- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-cr86-mm6w-6p6g

## What is CVE-2026-112345?

CVE-2026-112345 is a high-severity vulnerability in Sciener TTLock, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-112345?


## How do I fix CVE-2026-112345?

No fix has been published for CVE-2026-112345 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112345 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112345 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112345 and fix it if it is affected.

What it is: CVE-2026-112345 is a high-severity vulnerability in Sciener TTLock, published on 26 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112345 exists.

Affected product: Sciener TTLock. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112345/ (Markdown: https://insights.sbomify.com/CVE-2026-112345/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112345
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112345
- OSV: https://osv.dev/vulnerability/CVE-2026-112345

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112345/
Summaries are generated and may contain mistakes; the official description above is the record.