Is CVE-2016-20026 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-20026 being exploited in the wild.

How severe is CVE-2016-20026?

Critical severity, with a CVSS score of 9.8, published 16 March 2026.

Which products and versions are affected?

Zkteco ZKBioSecurity <= 3.0.1.0_R_230.

Is there a fix for CVE-2016-20026?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2016-20026 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2016-20026?

Check whether you run Zkteco ZKBioSecurity 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.

CVE-2016-20026: ZKTeco ZKBioSecurity hardcoded credentials in bundled Apache Tomcat

Q: Is there a fix for CVE-2016-20026?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2016-20026 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2016-20026?

Check whether you run Zkteco ZKBioSecurity 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.

CVE-2016-20026 · Severity: critical · CVSS 9.8 · Published 2026-03-16

ZKTeco ZKBioSecurity is an all-in-one security platform used for access control, video surveillance, and visitor management. A vulnerability in its bundled web server allows unauthenticated attackers to take full control of the system using known, preset login credentials. This could lead to unauthorized access to secure facilities, theft of sensitive biometric or visitor data, and complete disruption of security operations.

Technologies: Zkteco ZKBioSecurity. Vendors: Zkteco.

Quick answers

Is CVE-2016-20026 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-20026 being exploited in the wild.
How severe is CVE-2016-20026?: Critical severity, with a CVSS score of 9.8, published 16 March 2026.
Which products and versions are affected?: Zkteco ZKBioSecurity <= 3.0.1.0_R_230.
Is there a fix for CVE-2016-20026?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2016-20026 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-20026?: Check whether you run Zkteco ZKBioSecurity 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.

Technical details

ZKTeco ZKBioSecurity (up to version 3.0.1.0_R_230) bundles an Apache Tomcat server (version 7.0.56) with a pre-configured 'manager' application. The configuration file 'tomcat-users.xml' contains hardcoded credentials (username: 'zkteco', password: 'zkt123') with administrative roles including 'manager-gui' and 'manager-script'. An unauthenticated remote attacker can use these credentials to access the Tomcat Manager interface and deploy a malicious WAR archive containing a JSP webshell. Because the service typically runs with high privileges on Windows installations, this results in arbitrary code execution as 'nt authority\system'.

Affected products

ZKTeco ZKBioSecurity <= 3.0.1.0_R_230

Timeline

2016-07-18: disclosed: Vulnerability discovered by Zero Science Lab
2016-08-31: advisory: Public advisory and exploit released by Zero Science Lab and Exploit-DB
2026-03-16: advisory: CVE-2016-20026 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.