ZKTeco ZKBioSecurity 3.0 File Path Manipulation Vulnerability
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
ZKTeco ZKBioSecurity 3.0 contains a file path manipulation vulnerability that allows attackers to access arbitrary files by modifying file paths used to retrieve local resources. Attackers can manipulate path parameters to bypass access controls and retrieve sensitive information including configuration files, source code, and protected application resources.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2016-20029
- 2026-10-03 Alias added: GHSA-qwpg-chxq-r7gf
References
Exploit 2
Advisory 1
More ZKTeco vulnerabilities
- TI-2023-20210 A path traversal vulnerability in the iclock API of ZKTeco BioTime v8.5.5 allows… KEVCVSS 3.1HIGH 7.5
- TI-2025-28829 Hard-coded credentials in ZKTeco ZKBio CVSecurity CVSS 3.1CRITICAL 9.8
- TI-2024-24297 ZKTeco ZKBio CVSecurity v6.1.1 was discovered to contain a hardcoded cryptographic key. CVSS 3.1CRITICAL 9.8
- TI-2023-20211 ZKTeco BioTime 8.5.5 through 9.x before 9.0.1 (20240617.19506) allows authenticated… CVSS 3.1CRITICAL 9.8
- TI-2016-09202 ZKTeco ZKBioSecurity 3.0 Hardcoded Credentials Remote Code Execution CVSS 4.0CRITICAL 9.3
- TI-2016-09200 ZKTeco ZKTime.Net 3.0.1.6 Insecure File Permissions Privilege Escalation CVSS 4.0CRITICAL 9.3
Sources
- CVE-2016-20029 · CVE Program
- CVE-2016-20029 · NVD
- FIRST EPSS
- GHSA-qwpg-chxq-r7gf · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences