CVE-2024-36526: ZKTeco ZKBio CVSecurity · Use of Hard-coded Password
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Given the absence of an official patch, organizations should immediately engage with ZKTeco for updates or advisories. In the interim, restrict network access to ZKBio CVSecurity management interfaces to trusted internal networks only, using firewalls and network segmentation. Implement strict monitoring and logging of all authentication and cryptographic operations to detect anomalous activity indicative of exploitation attempts. Consider deploying additional layers of authentication or physical security controls to compensate for the compromised cryptographic key. Conduct a thorough audit of all devices and credentials managed by ZKBio CVSecurity to identify potential compromises. Plan for rapid deployment of vendor patches once available and test updates in controlled environments before production rollout. Educate security teams about the risks of hardcoded keys and ensure secure coding practices in future software development. Finally, maintain an incident response plan tailored to biometric and physical security system breaches.
Description
ZKTeco ZKBio CVSecurity v6.1.1 was discovered to contain a hardcoded cryptographic key.