# CVE-2026-108798: ZKTeco BioTime hard-coded cryptographic key

Source: https://junglewise.ai/threats/cve-2026-108798-a-vulnerability-was-found-in-zkteco-biotime-9-5-6-build-20260130  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-12. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-108798 · Severity: high · CVSS 7.3 · Published 2026-10-12

ZKTeco BioTime is a time and attendance management system used by organizations to track employee hours and access control. A flaw in BioTime 9.5.6 uses a hard-coded cryptographic key, allowing attackers on the network to decrypt communications or bypass security protections. This could lead to unauthorized access to employee records, attendance data manipulation, or system compromise.

Technologies: [Zkteco BioTime](https://junglewise.ai/threats/technologies/biotime). Vendors: [Zkteco](https://junglewise.ai/threats/vendors/zkteco).

## Quick answers

**Is CVE-2026-108798 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-108798 being exploited in the wild.

**How severe is CVE-2026-108798?** High severity, with a CVSS score of 7.3, published 12 October 2026.

**Which products and versions are affected?** Zkteco BioTime 9.5.6 Build 20260130.3206.

**Is there a fix for CVE-2026-108798?** Yes: fixed in 9.5.6 Build 3623. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-108798 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-108798?** Check whether you run Zkteco BioTime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 9.5.6 Build 3623

## Technical details

The vulnerability stems from the use of hard-coded cryptographic keys in BioTime's processing logic, allowing remote attackers to bypass cryptographic protections. The flaw exists in the base product without requiring authentication. An attacker can leverage this to decrypt sensitive communications or forge authenticated requests against the affected system.

## Affected products

- ZKTeco BioTime 9.5.6 Build 20260130.3206

## Timeline

- 2026-10-12: disclosed

## References

- [https://vuldb.com/cve/CVE-2026-108798](https://vuldb.com/cve/CVE-2026-108798)
- [https://vuldb.com/submit/961812](https://vuldb.com/submit/961812)

## Related threats

- [ZKTeco BioTime authorization bypass in Employee REST API](https://junglewise.ai/threats/cve-2026-108797-a-vulnerability-has-been-found-in-zkteco-biotime-9-5-6-build)
- [ZKTeco BioTime authorization bypass in biometric data endpoint](https://junglewise.ai/threats/cve-2026-108796-a-flaw-has-been-found-in-zkteco-biotime-9-5-6-build-20260130)
- [ZKTeco BioTime improper access control in system settings API](https://junglewise.ai/threats/cve-2026-108795-a-vulnerability-was-detected-in-zkteco-biotime-9-5-6-build)
- [ZKTeco BioTime SQL injection in database migration](https://junglewise.ai/threats/cve-2026-108794-a-security-vulnerability-has-been-detected-in-zkteco-biotime-9-5)
- [ZKTeco BioTime IDOR password disclosure in safe_setting endpoint](https://junglewise.ai/threats/cve-2025-15128-zkteco-biotime-idor-password-disclosure-in-safe-setting-endpoint)