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

> Attackers can exploit a hard-coded cryptographic key in ZKTeco BioTime to bypass security controls, requiring an upgrade to remediate.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-9jjc-qwqp-v5mv

## What is CVE-2026-108798?

CVE-2026-108798 is a medium-severity vulnerability in ZKTeco BioTime, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in ZKTeco BioTime 9.5.6 Build 20260130.3206. This issue affects some unknown processing. The manipulation results in use of hard-coded cryptographic key
 . The attack may be launched remotely. Upgrading to version 9.5.6 Build 3623 is capable of addressing this issue. It is suggested to upgrade the affected component.

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

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


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

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

## Is CVE-2026-108798 being exploited?

There is no known exploitation of CVE-2026-108798 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108798 is a medium-severity vulnerability in ZKTeco BioTime, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108798 in the wild and no public exploit code.

Affected product: ZKTeco BioTime. 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-108798/ (Markdown: https://insights.sbomify.com/CVE-2026-108798/index.md)
```

## Sources

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

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