---
title: "CVE-2026-112345: TTLock Android - Hardcoded Credentials"
description: "TTLock Android application < 9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key vulnerability caused by use of embedded defaultKey in BLE pairing, letting attackers within Bluetooth range decrypt session keys and perform unauthorized administrative actions without user interaction."
url: https://panop.io/threat-heartbeat/CVE-2026-112345/
---

# CVE-2026-112345 TTLock Android - Hardcoded Credentials

TTLock Android application < 9.8.260718 and associated smart-lock firmware contain a hardcoded static AES key vulnerability caused by use of embedded defaultKey in BLE pairing, letting attackers within Bluetooth range decrypt session keys and perform unauthorized administrative actions without user interaction.

CVSS base score 8.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-112345)

## Details

Type

Hardcoded Credentials

Impact

Broken Access Control

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Published

26 October 2026

Updated

27 October 2026

Weakness

[CWE-321](https://cwe.mitre.org/data/definitions/321.html)

## Vendor fix

Update to version 9.8.260718 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-112345](https://nvd.nist.gov/vuln/detail/CVE-2026-112345)
- [https://damiri.fr/en/cve/CVE-2026-112345](https://damiri.fr/en/cve/CVE-2026-112345)
- [https://www.vulncheck.com/advisories/ttlock-android-app-hardcoded-ble-pairing-key-exposure](https://www.vulncheck.com/advisories/ttlock-android-app-hardcoded-ble-pairing-key-exposure)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)